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.
Suggestion: mention canary/master branch system in the readme
See original GitHub issue- I have searched the issues of this repository and believe that this is not a duplicate.
Next.js breaks from GitHub convention by using canary as the default branch. I’m sure there are great reasons for this, but I think it’s important to flag it up in the readme, and perhaps even add navigation-style links at the top to switch between the ‘master’ and ‘canary’ readmes. I’d be happy to add this if you’re open to it.
This would help new users to avoid getting confused reading the wrong docs. It would also help users like me who want to get involved but who get put off by not being able to answer simple questions quickly and confidently, like which branch should I pull from, or PR into, etc.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:17
- Comments:5 (2 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
I second that. Spent the whole afternoon trying to make a custom
<App />work, because I read it in the documentation, only to find that it’s not out yet, despite being properly documented on the readme file.Only after seeing
canarymentioned in one of the issues related to the feature I understood what was going on. 😞Exactly, the upcoming stable release will be 7.0.0 as we’ve upgraded webpack and there are a few other breaking changes.