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.
Add upgrading guides
See original GitHub issueLooking at our traffic stats, a search for “Upgrading” is our 5th most visited page on the main repo:
We should add an upgrading guide for v1 -> v2 to the website, which would contain this information: https://github.com/styled-components/styled-components/releases/tag/v2.0.0 (it’s kinda funny because the actual upgrade is a simple npm install)
We should also make sure that we can add more upgrading guides in the future, i.e. that it’s extensible. (v2 -> v3, v3 -> v4, etc) Maybe we should just post our releases on the website? Is it possible to do that automatically based on the Releases page on GitHub? That’d be awesome for sure…
Issue Analytics
- State:
- Created 6 years ago
- Comments:17 (17 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
Better ? 😃
I guess, though that’s kinda weird. Maybe we should just get rid of the “Homepage” link (since the logo links there anyway) and add a “Releases” link at the end after “Ecosystem”, that’s probably better?