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.
Problem with package.json "engines" value, when using yarn
See original GitHub issueHi,
I have a problem with installing this package using yarn instead of npm. It says:
error react-easy-transition@1.2.3: The engine "node" is incompatible with this module. Expected version "7.2.1".
error Found incompatible module
As I understood it’s because of the value of engines.node, which in you case is strictly set to 7.2.1. Could you change it to something like 4.x || 5.x || 6.x || 7.x (it’s example from react’s package.json)?
Thanks!
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Running Yarn engines in package.json are ignore · Issue #2800
The engines field gets only checked for dependencies of your package. So you can specify that your package runs on a range of...
Read more >package.json - Yarn
The two most important fields in your package.json are name and version , without them your package won't be able to install. The...
Read more >The engine "node" is incompatible with this module
In my case, I am using yarn workspaces and some of the modules in the package.json files in the workspaces might require foo...
Read more >package.json
json file, and you can specify the engine using the "engines" field. (See below.) The name ends up being part of a URL,...
Read more >package.json - npm Docs
If you want to provide only a url, you can specify the value for "bugs" as a simple string instead of an object....
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
@misterfresh - Created a PR that should resolve this. #22
It should be good now