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.
Question: is there an expected Node/npm version for development?
See original GitHub issueI ran npm i and my package-lock.json was modified significantly from what’s in the repo. This generally happens if you run npm i using a different version of npm from what was used when package-lock.json was last updated. I’m using Node v12.7.0 and npm v6.13.1.
I looked into package.json file hoping to find the engines field which would tell me what version of Node and npm is expected but didn’t find it.
Suggestion: specify expected version of Node and npm in engines field of package.json.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@bolatovumar it will be different since the devDependencies aren’t version locked at the moment. This will result in you probably having a newer eslint, or a newer jest. Which will result in a different package-lock.json.
Issue-Label Bot is automatically applying the label
questionto this issue, with a confidence of 0.89. Please mark this comment with 👍 or 👎 to give our bot feedback!Links: app homepage, dashboard and code for this bot.