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.
Do not rename existing README, rename the CRA README
See original GitHub issueI would like to propose that instead of renaming existing README.md to README.old.md if any, CRA should instead leave that file alone and drop its readme under the name README-CRA.md and not README.md.
The rationale for this is that if a readme exists already, it’s most likely going to be more valuable than the CRA readme and that’s what people should keep seeing after CRA is scaffolded in the repository. It’s still handy to have the CRA readme handy, but no one is going to start rebuilding their existing readme on top the CRA one, they will just reference bits of the CRA one in their own.
So instead of forcing people to rename the CRA readme and fixing the incorrect rename of their already existing readme, let’s create the CRA readme under a new name and respect the exsting readme.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:7 (5 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
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.