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

Web3.storage is failed to npm install due to npm version #1416

Closed
IntelMin opened this issue Jun 8, 2022 · 2 comments
Closed

Web3.storage is failed to npm install due to npm version #1416

IntelMin opened this issue Jun 8, 2022 · 2 comments
Labels
kind/bug A bug in existing code (including security flaws)

Comments

@IntelMin
Copy link

IntelMin commented Jun 8, 2022

I was trying to run yarn add web3.storage.
Following error occurred. My node version is 14.17.5.

error ipfs-unixfs@6.0.9: The engine "node" is incompatible with this module. Expected version ">=16.0.0". Got "14.17.5"
error Found incompatible module.

I found that ipfs-unixfs@6.0.9 module is published a few days ago and this could be a reason of this error.
Is there anyway to install web3.stroage by not upgrading node to 16.0.0?

@IntelMin IntelMin added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Jun 8, 2022
@TeodorescuCostin
Copy link

Hi,
In the package.json the node engine version is specified as "16.x" so I think (but I am not 100% sure) that you would need to update it.
Here is the line of code:

"engines": {
    "node": "16.x",
    "npm": ">=7.x"
}

I think you can use NVM if you want to use multiple node versions.

@alanshaw alanshaw removed the need/triage Needs initial labeling and prioritization label Jun 20, 2022
@olizilla
Copy link
Contributor

Yes, @TeodorescuCostin is correct. We recommend you upgrade to node v16. node 14 is in maintenance mode and node 16 is active, and in ~3 months node 18 will be the thing.
see: https://nodejs.org/en/about/releases/

We don't have the bandwidth currently to make things work on node14 but if the diff is managable we're very open to PRs to make it work and add it to the test matrix.
see: #1014 (comment)

I'm going to close this as I think this issue is covered in #1014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws)
Projects
None yet
Development

No branches or pull requests

4 participants