Closed ChazUK closed 2 years ago
We've had this issue multiple times as well. Using next@canary
was the main trick to overcome this. Also re-generating the package-lock.json
might help.
We've had this issue multiple times as well. Using
next@canary
was the main trick to overcome this. Also re-generating thepackage-lock.json
might help.
Thanks @webpro. that kind of raises other issues but it's a lead...
We're trying to upgrade to node 16 and see this exact error in Github Actions, and unfortunately regenerating package-lock.json
doesn't help. The identical repo works fine under node 14.
We resolved this by explicitly adding the @swc/core
package to our devDependencies
This is a duplicate of https://github.com/nrwl/nx/issues/8969
Check this comment or this comment for the potential solution.
The core of the problem is in the lock file missing the optional dependencies requested by @swc/core
.
Make sure you run npm ci
on your CI and do not provide a skip-optional
flag.
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.
I'm having an issue running my linting tasks on my CI server. The error message that comes up is that the module can't be found for @swc/core. Is it possible to find out exactly what version it's trying to install? Or is this a problem with eslint 8?
npm list --depth=0 here https://gist.github.com/ChazUK/2cda2da98ae9b3092357aae6b96671c1
and Nx Report is also below