Skip to content
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

Preparing the next release #3672

Closed
gaearon opened this issue Jan 2, 2018 · 19 comments
Closed

Preparing the next release #3672

gaearon opened this issue Jan 2, 2018 · 19 comments

Comments

@gaearon
Copy link
Contributor

gaearon commented Jan 2, 2018

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.

@gaearon gaearon changed the title Preparing next release Preparing the next release Jan 2, 2018
@andreicek
Copy link

I'm not sure if #3522 is ready, but it's a great feature that would work really well for typescript 😄

@gaearon
Copy link
Contributor Author

gaearon commented Jan 2, 2018

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.

@DarkoKukovec
Copy link

I didn't find a PR for it, but asset inlining (#1944/#2961) or svg importing (#1388) would be awesome.

@kentcdodds
Copy link
Contributor

kentcdodds commented Jan 2, 2018

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).

@darrenscerri
Copy link
Contributor

There's #2011 which is ready.

@gaearon
Copy link
Contributor Author

gaearon commented Jan 2, 2018

Cool, I'd take a PR for #2730.

@gaearon
Copy link
Contributor Author

gaearon commented Jan 2, 2018

(See my only concern in #2730 (comment))

@andriijas
Copy link
Contributor

How about #2285 and:or #2206

@clentfort
Copy link

Would love to see #3590 included.

@kentcdodds
Copy link
Contributor

PR opened to close #2730 :) #3675

@tharakawj
Copy link
Contributor

I guess we can merge #3465 and think about supporting eslint errors separately.

@viankakrisna
Copy link
Contributor

#2755 #3350 and #3618 ?

@bjoernricks
Copy link

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.

@bondz
Copy link
Contributor

bondz commented Jan 3, 2018

#3408 exposing the --info flag is ready.

@omeid
Copy link

omeid commented Jan 3, 2018

@gaearon Please consider #3675 for this release. I understand it might be released unsupported and that is fine, macros would open up the adoption of CRA to many many people who now have to eject or don't use CRA altogether.

@gaearon
Copy link
Contributor Author

gaearon commented Jan 6, 2018

We’ll also need to solve #3638. It’s really sad people keep breaking their own setups.

@piotr-cz
Copy link
Contributor

Adding #3375 into release could help in moving #2426 forward and few people in meanwhile.

@ro-savage
Copy link
Contributor

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.

@gaearon
Copy link
Contributor Author

gaearon commented Jan 16, 2018

I published a roadmap to 2.x in this issue: #3815
Please let me know what you think!

@gaearon gaearon closed this as completed Jan 16, 2018
@lock lock bot locked and limited conversation to collaborators Jan 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests