Description
Let’s discuss the next releases.
0.9.1
Hi Pri
For 0.9.1, I feel strongly we should release it asap so that we can land more breaking changes without cherry-picking stuff. In particular I want to see these fixed:
-
Figure out how to deal with slashes in Jest: Jest does not validate <rootDir> reference in some environments #1417, eject command on windows creates different path sepalators to package.json #1498. This should be easy to fix—perhaps it's enough to just use forward slashes everywhere. I just want to make sure we test this works on Windows, and fix it once and for all. I’m happy to test any given PR on Windows if you think you have something that should work and just need confirmation.
-
Fix
npm link
for people who forkreact-scripts
Fix workflow if react-scripts package is linked via npm-link #1356 -
Gracefully handle installation failures Gracefully handle initial installation error (#1505) #1512
Lo Pri
I don't feel strongly about these ones:
-
Jest.mock does not resolve modules correctly when NODE_PATH is set (Jest.mock does not resolve modules correctly when NODE_PATH is set #1271).
-
CSS dependency with private module @import fails (CSS dependency with private module @import fails with #1290)
-
npm version check (NPM version check for tip #1193)
-
Some e2e test failure with forking
react-scripts
. e2e tests fail because of missing package.json #1401. Should be easy to look into and decide.
We could postpone looking into them until 0.9.2 or 0.10. I don't want them holding off 0.9.1 release.
0.9.4
Bugs:
- Jest.mock does not resolve modules correctly when NODE_PATH is set (Jest.mock does not resolve modules correctly when NODE_PATH is set #1271).
Things we should stabilize before the next breaking release, but not necessarially blocking (this would have to be in 0.10):
- CSS dependency with private module @import fails (CSS dependency with private module @import fails with #1290)
We want to make tracking react-scripts
painless:
- Some e2e test failure with forking
react-scripts
. e2e tests fail because of missing package.json #1401. Should be easy to look into and decide. - Scoped packages should work with our CLI: Scoped packages on forked versions #1414
0.10.0
There's a lot of stuff there to still get in.
I want to merge #1101 and release a canary so that people can start playing with it (cc @kittens). It shouldn't be an official release because we still have a bunch of known issues with 0.10.
After we cut 0.9.1 0.9.4 we can write a clearer roadmap here.
Plan
I guess at this point we just need somebody willing to get 0.9.1 to the point where it’s ready. @Timer Could you do this? Alternatively we can ask somebody else to help with the release, or maybe I could give it some time next week.
We should focus on stabilizing and releasing the final 0.9.x release, then begin focusing on 0.10 and addressing all the underlying bugs which are blocking us, performing upstream reporting & triaging where necessary.