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

Due to a bug in npm v7, Currently, node.js v16.x should be used for evaluation purposes. #891

Closed
nxhack opened this issue May 6, 2021 · 3 comments

Comments

@nxhack
Copy link
Owner

nxhack commented May 6, 2021

Ref: npm/cli#2339
Ref: npm/cli#3175
Ref: npm/cli#3192

Ref: npm/cli#2900
Ref: npm/cli#1969
Ref: npm/cli#2921

@nxhack nxhack pinned this issue May 6, 2021
@nxhack
Copy link
Owner Author

nxhack commented May 7, 2021

There are some breaking changes in npm v7. There are also probably quite a few bugs.
To get around this, I decided to downgrade npm to v6.

@nxhack
Copy link
Owner Author

nxhack commented May 16, 2021

The npm v7 support is now in the master branch, and the way to create node modules has been significantly changed. I haven't tested everything yet, so please report any problems.

d686699

@nxhack nxhack changed the title Due to a bug in npm v7, please do not use node.js v16.x for now. Due to a bug in npm v7, Currently, node.js v16.x should be used for evaluation purposes. May 17, 2021
@nxhack
Copy link
Owner Author

nxhack commented May 20, 2021

With node v16.2.0, npm is now v7.13.0.
I'll adjust with npm v7 from now on.

@nxhack nxhack closed this as completed May 20, 2021
@nxhack nxhack unpinned this issue May 21, 2021
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