Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unable to install v3.0.0 on node 6.14.0
See original GitHub issueSince today I’m unable to install tough-cookie on node v6.14.0, because I’m getting the following error:
error ip-regex@3.0.0: The engine "node" is incompatible with this module. Expected version ">=8". Got "6.14.0"
I suspect that the introduction of ip-regex in PR #138 (and especially this commit) causes that, because ip-regex ^3.0.0 needs at least node v8.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Prevent npm install for not supported Node.js versions
It displays a warning but is not failing and preventing the user from going on. How to prevent npm install with an unsupported...
Read more >How do I upgrade npm to support Node.js v14.0.0 on ...
Try : Mac: sudo npm uninstall -g npm // uninstalls globally Windows: npm uninstall -g npm // uninstalls globally. Then: Re-install node.
Read more >How to install the latest versions of NodeJS and NPM?
Use the NodeSource PPA. For details look at the installation instructions. First, choose the Node.js version you need and add the sources for...
Read more >Solved: [ERROR] Failed to execute goal com.github.eirslett...
1. Please install latest node js update npm version in pom. 2.use below command. Mvn clean install -padobe-public.
Read more >Download & Update Node.js to the Latest Version! ...
Node v19.0.0 Current / LTS v16.18.0 Direct Links ... Additionally the agent is now able to parse the response Keep-Alive which the servers ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes with that flag I’m able to bypass the issue and install tough-cookie, but does that doesn’t solve the actual problem. I think tough-cookie should either depend on an older version of ip-regex, or enforce node >=8 as well.
I’m sorry that I didn’t get this resolved sooner. This is pretty much all on me. This fix has been published as version 3.0.1.
To be totally honest with you, I’m stretched incredibly thin for time as I’m trying to get my business started up. Me, and the folks from Salesforce meet on a monthly basis to discuss bugs and pull requests. I then spend that day and maybe the day after, tops, working on tough-cookie before returning to my other tasks. This is more frequently than change happened historically, but clearly isn’t reactive enough. I could be doing fixes like this if I had additional bandwidth, but I don’t; I’m having a hard time justifying working for free versus working to get to the point where I’m not living off of savings.
If you know someone who’d like to help co-maintain tough-cookie, please send them our way; we’d love the help.