-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
[Bug]: Possible breaking change for node v14.16.0 #4184
Comments
Thank you. If you add |
Thank you for the quick response and fix! Will do so |
The new version solved the problem with the worker_threads module, but there seems to be other parts that were affected by similar problems, such as in |
I doubled checked, it had passed all the tests on 14.x (latest). |
That's interesting, the problem seems to come from the @cspell/dynamic-import package, in the cjs/index.cjs where |
Things run on 14.21 that will not run on 14.16. It is not even possible to build the app on 14.16. RollupJS crashes. |
Thank you for the information, I will forward this to my team and perhaps consider upgrading the node version. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Kind of Issue
Crash / Error
Tool or Library
cspell
Version
from 6.22.0
Supporting Library
Not sure
OS
Macos
OS Version
v12.6.1
Description
Possible breaking change for node v14.16.0
Current project is running on node v14.16.0 and had lint-staged setup to perform spell check before git commit through npx cspell.
The error
Cannot find module 'node:worker_threads'
occur during npx cspell at the cspell/dist/util/cache/fileEntryCache.js file.
Reverting cspell version by installing a local version of cspell pre 6.22.0 with
npm -g install cspell@6.21.0
remove the errorSteps to Reproduce
npx cspell .
without cspell installed locallynpm -g install cspell@6.21.0
npx cspell .
againExpected Behavior
No response
Additional Information
No response
cspell.json
cspell.config.yaml
No response
Example Repository
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: