You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Document how to upgrade react-scripts after creating an app #119
Yeah, I think editing package.json or npm update will do it but it hasn't been documented. Just posting here to see if we want something more than that.
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 react-scripts - if you're on an older, more-stable version, and you're happy with it, then just keep being happy with it. We also might release a breaking change in react-scripts at some point and then an automated message that encourages people to update would be counterproductive.
Reacted by Keyan Zhang, Mark Erikson, Max Stoiber and dan
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.
Activity
dolchi21 commentedon Jul 23, 2016
would editing the package.json dep and installing do it? (always checking for compatibility errors)
keyz commentedon Jul 23, 2016
Yeah, I think editing
package.jsonornpm updatewill do it but it hasn't been documented. Just posting here to see if we want something more than that.lacker commentedon Jul 23, 2016
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
react-scripts- if you're on an older, more-stable version, and you're happy with it, then just keep being happy with it. We also might release a breaking change inreact-scriptsat some point and then an automated message that encourages people to update would be counterproductive.mxstbr commentedon Jul 23, 2016
Totally agree with @lacker.
We've had this discussion quite a few times over at
react-boilerplate– whatever version you use will work perfectly fine, there's no need to upgrade!gaearon commentedon Jul 23, 2016
We actually should document that so reopening.
But I agree we shouldn’t ask people to update.
ForbesLindesay commentedon Jul 25, 2016
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.
insin commentedon Jul 25, 2016
If they're not running
npm out --depth=0on a regular basis, they don't deserve your sweet new features 😸Add updating instructions
cesarvarela commentedon May 31, 2017
i need a feature that is on
1.0.0and myreact-scriptsare in0.9.5how do I update them?gaearon commentedon May 31, 2017
You can find the instructions in release notes, as always.
https://github.com/facebookincubator/create-react-app/releases/tag/v1.0.0
simonw commentedon Apr 30, 2018
I'm seeing this warning on a project I created using create-react-app:
Official documentation on how to upgrade would be really useful.
Timer commentedon Apr 30, 2018
Documentation on how to upgrade is on every release.
https://github.com/facebook/create-react-app/releases