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.
Drop support for Node 8; test in Node 13
See original GitHub issueNode 8 hit end of life on 12/31 so it’s time to drop support for it.
That’s a breaking change for Nock and normally I like to batch up the breaking changes to avoid super-frequent semver major bumps. There are a few TODOS marked TODO-12.x which I’d like to push through at the same time.
We could merge some of these on the beta branch. Should we force push master to beta and then start pushing this work through?
The last time we released from the beta branch, we ended up needing to rewrite history on the commits when they were released (beta is currently on c0be8f884f85aea8662833869bd754f40c38d5da which is 235 commits ahead and 334 commits behind master). I want to try to avoid that this time, if we can!
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (10 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
An initial
git push --forcebase on latestmasteris fine, it won’t destroy any history. The new beta has nothing todo with the old beta. Ideally we would delete the beta branch once we merge a PR frombetaintomasterThe
close #XYZwill only be applied once the commits are merged into the repositories main branch.