-
Notifications
You must be signed in to change notification settings - Fork 52
2.1.3 ERROR: ErrorStackParser.parse is not a function #80
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
Comments
Looking forward to repairing as soon as possible. |
i hope some one can fixing this bug :( |
Possibly related to #75 |
This breaks all our webpack builds. |
I suspect that this change is breaking a lot of people's CI today :( Please roll back this change immediately. |
Same here.. |
This broke our webpack builds as well. |
Now the projects have failed to build, I can compile normally after I force the installation of version 2.0.6 |
@nzhernovkov I tried setting Does your project use vue at all? Can you offer any advice? @eriwen Please revert this change ASAP. |
@jonesnc My project uses vue cli, my devDependencies configuration:
|
@zhouxianjun thanks |
see your package-json.lock
|
@zhouxianjun Adding error-stack-parser 2.0.6 to the devDependencies is leading to 2 versions of it being installed, the first being requested by @soda/friendly-errors-webpack-plugin@^1.7.1 which is a dependency of vue cli service.
Edit: Found the fix
|
@Siddharth24Khera does that |
Yes,
|
@Siddharth24Khera Thanks, I think that fixed it for me. |
THANK YOU! I tried to fix this by 3 hours... |
I've had luck working around this issue by using the new "overrides" functionality in NPM 8.3 or greater: https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides Hopefully this issue gets resolved in the actual package itself shortly. |
Resolvemos esse problemas aplicando ao package.json do projeto: He just solved this issue, applying this in package.json file: |
so we should never install this version (2.1.3) ? |
Hope, |
Был здесь до того как это стало мемом... |
We have deprecated v2.1.3, v2.1.2, v2.1.1, v2.1.0, and v3.0.0 using @eriwen please use Looking at fixing this unless @eriwen beats us to it. |
v2.1.4 released to npm and GitHub https://github.com/stacktracejs/error-stack-parser/releases/tag/v2.1.4 @eriwen I reverted those commits that caused the breaking change (when you implement them and upgrade to support both CJS/ESM then perhaps revert and publish a new major semver version). Note I used |
Thanks, @titanism, I can confirm 2.1.4 works for Serenity/JS too. |
Thanks @titanism for fixing. I thought I had reverted the breaking commit before releasing 2.1.3. np is a good suggestion I'll use going forward. |
|
Thanks a lot! |
After upgrading the version to 2.1.3, we get this error.
Current Behavior
ERROR: ErrorStackParser.parse is not a function
Steps to Reproduce (for bugs)
Context
Your Environment
The text was updated successfully, but these errors were encountered: