question-mark
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.

Node versions should be consistent

See original GitHub issue

The engine versions, Travis versions, and recommended version from the readme should be consistent. See #935 and #1050.

Potential solutions

(mutually exclusive)

  1. Support 6 by testing it for users that may need to use it with Babel, otherwise it should not be in Node engines because it may be broken. Documentation (Readme.md and docs/api/index.md) should make it clear that 6 is required but 7.6 is recommended. 6 should be added to Travis versions.
  2. Revert #935 and the Node 6 support added in 2.0.1. Engines should be >= 7.6.0. Other versions can be left alone since using 6 would be discouraged.

Current semver version ranges

Node engines

>= 6.0.0

Recommended versions in documentation

>= 7.6.0

Travis builds

(similar to doc versions, Travis only installs the latest versions of major releases)

7 and 8

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:6 (4 by maintainers)

github_iconTop GitHub Comments

2reactions
jonathanongcommented, Apr 28, 2020

at this point i’d just like >= 10

1reaction
JasonBoycommented, Dec 6, 2017

@jonathanong create a PR #1103 to sync node version ^7.10.1 in Readme.md with package.json/engines

Read more comments on GitHub >

github_iconTop Results From Across the Web

Node Version Managers and why you need one - POATEK
Consistent node version adoption inside the team: if everyone on the team is using the same node version then npm will be 100%...
Read more >
Consistent dependencies across teams - Kostas Bariotis' Blog
A common pitfall when comes to development teams is the inconsistent software and library versions across developers.
Read more >
Understanding How Node.js Release Lines Work - NodeSource
The Node.js release process can seem complex and burdensome at times. Dig deep into the release process, its terminology, and its timelines ...
Read more >
How can I specify the required Node.js version in package.json?
I have a Node.js project that requires Node version 12 or higher. Is there a way to specify this in the packages.json file,...
Read more >
Ensure Node.js version is consistent on Azure services and ...
You should ensure that the versions of Node.js you know that your code works with are specified to npm. This is achieved using...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found