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.
Strategy for supporting node versions
See original GitHub issueI was going through the LTS schedule for node. And at time of writing it looks like:
Currently I’m a bit confused on what strategy we should pick. Updating .travis.yml etc feels a bit random to me atm. Therefore I’d like us to have a clear strategy on which versions we should support and test on.
Here are some alternatives:
EDIT: Poll locked.
With “enough es6 features” I mean at least have support for destructuring (since we currently started using this for levelup@2.0.0)
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (14 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
@vweevers If we follow what @mcollina suggested, we will still support node 7 on older versions of levelup, so we can safely drop support from some versions as long as we bump major.
@ralphtheninja exactly. V2 would support 6, 8, 9 and 10, then V3 will be 8, 10, 11 and 12. And so on.