-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document how to upgrade react-scripts after creating an app #119
Comments
would editing the package.json dep and installing do it? (always checking for compatibility errors) |
Yeah, I think editing |
Imagine if every npm module you installed, also prompted you to upgrade it when there's a new version. That would be pretty annoying. ;-) For a lot of people, there's actually no reason to upgrade |
Totally agree with @lacker. We've had this discussion quite a few times over at |
We actually should document that so reopening. |
This is also a little different to react-boilerplate. Updating a boilerplate doesn't really make sense/is a nightmare to do. On the other hand we plan for most updates to react-scripts to be backwards compatible, but there could be performance enhancements and new features. For this reason I think we should suggest that people may want to upgrade. I probably don't think we should prompt people to upgrade though, just suggest that they do in the documentation. |
If they're not running |
i need a feature that is on |
You can find the instructions in release notes, as always. |
@gaearon if I am on |
It might seem like a silly question and it is. I was imagining that some sort of local data or config had to change. However (duh) there is no build configuration here or anything else to migrate. So I think the answer is probably: No. I do not need to install each version individually. Sorry for asking silly questions! |
Documentation on how to upgrade is on every release. |
Also, can we add a version checking that prompts users to upgrade their
react-scripts
dependency when there's a new version? :)The text was updated successfully, but these errors were encountered: