-
-
Notifications
You must be signed in to change notification settings - Fork 27k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Preparing the next release #3672
Comments
I'm not sure if #3522 is ready, but it's a great feature that would work really well for typescript 😄 |
It’s not ready. There’s a bug in Babel that we don’t understand yet, and it’s not a stable release we could use. |
Whelp... you did ask: #2730 <3 (Sorry, not a PR, but if you're willing, I'd make a quick PR for it... It could/should be released as an experimental undocumented feature at first). |
There's #2011 which is ready. |
Cool, I'd take a PR for #2730. |
(See my only concern in #2730 (comment)) |
Would love to see #3590 included. |
I guess we can merge #3465 and think about supporting eslint errors separately. |
Would love to see something like #2206 in the next release. Speeding up the production build time has such a great benefit for us. Currently CircleCI needs ~4 minutes for a full build. |
#3408 exposing the |
We’ll also need to solve #3638. It’s really sad people keep breaking their own setups. |
CSS Modules #2285 can be cut for release. I will bring across the latest changes from https://github.com/ro-savage/react-scripts-cssmodules in the next 48hrs and should be ready to go. |
I published a roadmap to 2.x in this issue: #3815 |
It's been a while since I cut a release but I should have some time the next couple of weeks. What's ready enough that we can get this in? I was thinking of updating Jest to 22, but are there other PRs that are almost ready? It's okay if those are breaking changes since Jest update itself is a breaking change.
The text was updated successfully, but these errors were encountered: