Skip to content

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

Closed
nzhernovkov opened this issue Jun 6, 2022 · 29 comments
Closed

2.1.3 ERROR: ErrorStackParser.parse is not a function #80

nzhernovkov opened this issue Jun 6, 2022 · 29 comments
Labels

Comments

@nzhernovkov
Copy link

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

  • Package version: 2.1.3
@Harry-wyg
Copy link

Looking forward to repairing as soon as possible.

@elvandiano
Copy link

i hope some one can fixing this bug :(

@jan-molak
Copy link

Possibly related to #75

@AuspeXeu
Copy link

AuspeXeu commented Jun 6, 2022

This breaks all our webpack builds.

@stevenmhunt
Copy link

I suspect that this change is breaking a lot of people's CI today :( Please roll back this change immediately.

@Harry-wyg
Copy link

image

requirejs has not module.exports.default

@awcs
Copy link

awcs commented Jun 6, 2022

Same here..

@jonesnc
Copy link

jonesnc commented Jun 6, 2022

This broke our webpack builds as well.

@zhouxianjun
Copy link

Now the projects have failed to build, I can compile normally after I force the installation of version 2.0.6

@jonesnc
Copy link

jonesnc commented Jun 6, 2022

@nzhernovkov I tried setting "error-stack-parser": "2.0.6", in my dependencies, my project also uses @vue/cli-service which also depends on error-stack-parser, and I'm still getting the error.

Does your project use vue at all? Can you offer any advice?

@eriwen Please revert this change ASAP.

@zhouxianjun
Copy link

@jonesnc My project uses vue cli, my devDependencies configuration:

"@vue/cli-plugin-babel": "~4.5.0",
"@vue/cli-plugin-eslint": "~4.5.0",
"@vue/cli-plugin-router": "~4.5.0",
"@vue/cli-plugin-typescript": "~4.5.0",
"@vue/cli-plugin-vuex": "~4.5.0",
"@vue/cli-service": "~4.5.0",
"error-stack-parser": "2.0.6", // this line fix the error

@danilsdf
Copy link

danilsdf commented Jun 6, 2022

@zhouxianjun thanks
I have added "error-stack-parser": "2.0.6" to package.json and it fixes it

@zhouxianjun
Copy link

@nzhernovkov I tried setting "error-stack-parser": "2.0.6", in my dependencies, my project also uses @vue/cli-service which also depends on error-stack-parser, and I'm still getting the error.

Does your project use vue at all? Can you offer an advice?

@eriwen Please revert this change ASAP.

see your package-json.lock

"error-stack-parser": {
  "version": "2.0.6",
  "resolved": "",
  "integrity": "sha1-WpmnB716TFinl5AtSNgoA+3mqtg=",
  "dev": true,
  "requires": {
    "stackframe": "^1.1.1"
  }
}

@Siddharth24Khera
Copy link

Siddharth24Khera commented Jun 6, 2022

@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.

"@soda/friendly-errors-webpack-plugin@^1.7.1":
  version "1.8.1"
  resolved "https://registry.yarnpkg.com/@soda/friendly-errors-webpack-plugin/-/friendly-errors-webpack-plugin-1.8.1.tgz#4d4fbb1108993aaa362116247c3d18188a2c6c85"
  integrity sha512-h2ooWqP8XuFqTXT+NyAFbrArzfQA7R6HTezADrvD9Re8fxMLTPPniLdqVTdDaO0eIoLaAwKT+d6w+5GeTk7Vbg==
  dependencies:
    chalk "^3.0.0"
    error-stack-parser "^2.0.6"
    string-width "^4.2.3"
    strip-ansi "^6.0.1"

error-stack-parser@2.0.6:
  version "2.0.6"
  resolved "https://registry.yarnpkg.com/error-stack-parser/-/error-stack-parser-2.0.6.tgz#5a99a707bd7a4c58a797902d48d82803ede6aad8"
  integrity sha512-d51brTeqC+BHlwF0BhPtcYgF5nlzf9ZZ0ZIUQNZpc9ZB9qw5IJ2diTrBY9jlCJkTLITYPjmiX6OWCwH+fuyNgQ==
  dependencies:
    stackframe "^1.1.1"

error-stack-parser@^2.0.6:
  version "2.1.3"
  resolved "https://registry.yarnpkg.com/error-stack-parser/-/error-stack-parser-2.1.3.tgz#ab877c676540507dbe6429974ea66833ae68b7cb"
  integrity sha512-F9KypcaAvLzI4yXneZzOvzZoqakhbjuAGFK0aLy33tYaDqdu6v+lzrN/TTG/mM48Op624zZZ2RpXRx3wA0+zmg==
  dependencies:
    stackframe "^1.3.4"

Edit: Found the fix
For yarn, I used resolutions to force version 2.0.6

 "resolutions": {
    "error-stack-parser": "2.0.6"
  }

@jonesnc
Copy link

jonesnc commented Jun 6, 2022

@Siddharth24Khera does that "resolutions" setting go in the package.json file?

@Siddharth24Khera
Copy link

@Siddharth24Khera does that "resolutions" setting go in the package.json file?

Yes,

  "devDependencies": {
    "@vue/cli-plugin-babel": "^3.4.0",
    "@vue/cli-plugin-eslint": "^3.4.0",
    "@vue/cli-plugin-pwa": "^3.4.0",
    "@vue/cli-service": "^3.4.0",
    "sass": "^1.49.11",
    "sass-loader": "^7.1.0",
    "vue-template-compiler": "^2.6.6",
    "error-stack-parser": "2.0.6"
  },
  "resolutions": {
    "error-stack-parser": "2.0.6"
  }

@jonesnc
Copy link

jonesnc commented Jun 6, 2022

@Siddharth24Khera Thanks, I think that fixed it for me.

@Katerinka28
Copy link

Katerinka28 commented Jun 6, 2022

@Siddharth24Khera does that "resolutions" setting go in the package.json file?

Yes,

  "devDependencies": {
    "@vue/cli-plugin-babel": "^3.4.0",
    "@vue/cli-plugin-eslint": "^3.4.0",
    "@vue/cli-plugin-pwa": "^3.4.0",
    "@vue/cli-service": "^3.4.0",
    "sass": "^1.49.11",
    "sass-loader": "^7.1.0",
    "vue-template-compiler": "^2.6.6",
    "error-stack-parser": "2.0.6"
  },
  "resolutions": {
    "error-stack-parser": "2.0.6"
  }

THANK YOU! I tried to fix this by 3 hours...

@stevenmhunt
Copy link

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.

@legsilva
Copy link

legsilva commented Jun 6, 2022

Resolvemos esse problemas aplicando ao package.json do projeto:
"resolutions": {
"error-stack-parser": "2.0.6"
},

He just solved this issue, applying this in package.json file:
"resolutions": {
"error-stack-parser": "2.0.6"
},

@brucemeteor
Copy link

so we should never install this version (2.1.3) ?

@Katerinka28
Copy link

Katerinka28 commented Jun 6, 2022

so we should never install this version (2.1.3) ?

Hope, @soda/friendly-errors-webpack-plugin will fixed import of error-stack-parser as soon as possible.
They used require(...) by 6 year...

@s1lentssh
Copy link

Был здесь до того как это стало мемом...

@titanism
Copy link
Collaborator

titanism commented Jun 6, 2022

We have deprecated v2.1.3, v2.1.2, v2.1.1, v2.1.0, and v3.0.0 using npm deprecate error-stack-parse@X.X.X "Please upgrade to error-stack-parser >= v2.1.4, see https://github.com/stacktracejs/error-stack-parser/issues/80".

@eriwen please use np to publish new versions, it will help with versioning and prevent breaking errors. Also for anything with ESM/CJS changes or import/export changes, we should have done a major semver version release. See https://github.com/sindresorhus/np.

Looking at fixing this unless @eriwen beats us to it.

@titanism
Copy link
Collaborator

titanism commented Jun 6, 2022

v2.1.4 released to npm and GitHub

https://github.com/stacktracejs/error-stack-parser/releases/tag/v2.1.4
https://www.npmjs.com/package/error-stack-parser/v/2.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 np to release v2.1.4, and it also makes a nice Release page for us.

@titanism titanism closed this as completed Jun 6, 2022
@jan-molak
Copy link

Thanks, @titanism, I can confirm 2.1.4 works for Serenity/JS too.

@eriwen
Copy link
Member

eriwen commented Jun 7, 2022

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.

@Archie2035
Copy link

"error-stack-parser": "2.0.6"
Thanks a lot!

@Archie2035
Copy link

Thanks a lot!

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

No branches or pull requests