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.

Sign up for GitHub

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

Jump to bottom

Can't install w3 cli on node 14 with npm 6 #387

Closed
andrew opened this issue Aug 23, 2021 · 0 comments · Fixed by ipfs/js-ipfs-unixfs#167 or #404
Closed

Can't install w3 cli on node 14 with npm 6 #387

andrew opened this issue Aug 23, 2021 · 0 comments · Fixed by ipfs/js-ipfs-unixfs#167 or #404
Assignees
@vasco-santos
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization

Comments

@andrew
Copy link

andrew commented Aug 23, 2021

Dependency of w3, ipfs-unixfs currently requires npm 7 or greater to install, trying to install on node 14 with npm 6 results in an error:

npm WARN notsup Unsupported engine for ipfs-unixfs@5.0.0: wanted: {"node":">=14.0.0","npm":">=7.0.0"} (current: {"node":"14.17.5","npm":"6.14.14"})
npm WARN notsup Not compatible with your version of node/npm: ipfs-unixfs@5.0.0

node 14 and npm 6 are the default latest versions installed on the snap store: https://snapcraft.io/node, also the latest LTS release I think so it would be good to be able to use it without needing to upgrade the package manager.
@andrew andrew added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Aug 23, 2021
@vasco-santos vasco-santos self-assigned this Aug 25, 2021
@vasco-santos vasco-santos mentioned this issue Aug 25, 2021
Merged
achingbrain pushed a commit to ipfs/js-ipfs-unixfs that referenced this issue Aug 25, 2021
@vasco-santos
fix: individual packages can use npm 6 (#167)
2b429cc 
We have engines with npm7 because we use npm7 workspaces, but this should only be needed in the main package.json for development. Internal packages should be published as supporting npm6 given that there are linux environments that still do not support npm7. For more information see web3-storage/web3.storage#387 where this issue was raised

Closes web3-storage/web3.storage#387
@vasco-santos vasco-santos mentioned this issue Aug 26, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vasco-santos vasco-santos

Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization
Projects
None yet
Milestone
No milestone
2 participants
@andrew @vasco-santos