Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Unexpected token" when analyzing after upgrading marked #42

Open
rejas opened this issue Jun 17, 2023 · 0 comments
Open

"Unexpected token" when analyzing after upgrading marked #42

rejas opened this issue Jun 17, 2023 · 0 comments

Comments

@rejas
Copy link

rejas commented Jun 17, 2023

I noticed that our packtracker.io webpack-plugin started reporting bogus values after our latest "npm update" run.

Our logs show this error from the analyzer:

Unexpected token (1:245361)

This points to the updated markedjs package, right into the middle of this codeline:

https://github.com/markedjs/marked/blob/4c1a164f70c3fecf83286a2723e8c067eb782817/src/Hooks.js#L8

Downgrading only that package from v4.3.0 to v4.2.12 fixes the error and the packtracker stats are ok again.

Not sure why the parser doesn't like this line / codechange though, running the analyzer with the CLI directly from our code doesn't bring this error.

Already reported to webpack-bundle-analyzer (webpack-contrib/webpack-bundle-analyzer#595) but wanted to get your feedback too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant