-
-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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
Roadmap for react-scripts@2.0 #3815
Comments
Hi, @gaearon! I'm really excited about this announcement. The create-react-app is a important tool in my work and side projects. I don't have experience with open source projects and the source code of create-react-app but I would like to contribute. Do you think that people with no experience could contribute? |
Sure, maybe! Please message me on Twitter. |
We have released the first alpha version of Please let us know of any bugs in new issues, thanks! |
It'd also be great if React Hot Loader (https://github.com/gaearon/react-hot-loader/tree/next) could be integrated in, if its matured to that point. I really miss having forms stay filled in when editing code. |
I'd like to suggest #3834 as well to be included in the next release 🙂 |
Tried 2.0 with a large app that uses react-app-rewire to extend some config (add less support) and the transition is flawless. 👍 |
It would be great if there's finally support for postcss without ejecting |
@ChuksFestus Which specific postcss plugins? There's been a lot of discussion about how "custom properties" plugin is not actually future-proof and not safe to enable by default. Are there others you consider safer? Note we don't want people to lock themselves into using features that aren't actually going to be a part of CSS in the future. |
What about cssnext - the "babel" for css: http://cssnext.io ? As a sidenote, is it possible to import variables or plain css from other .css files from a .modules.css file currently in CRA? The upcoming CSS modules is very welcome, but for theming we need to import and reference CSS in other .css files within them as well. |
It would be nice to support custom ESLint preset without ejecting. I understand the philosophy of not wanting to have any config files, but in many cases it become very annoying:
Don't get me wrong, I fully understand your philosophy and admire your work. But, on the other hand you lock me with your "configuration" for a linter with specific rules which makes me it harder work for me than not having it from the first place, which there is no easy way to opt out without ejecting. Moreover, you actually do have configurations such as |
I think it quickly becomes unfeasible if there is more than one or two configurations to be supported - but being able to eject one can always break free in "unsupported land". The only downside is to not being able to upgrade to new versions of react-scripts anymore. Therefore, what I think would be nice is to be able to record the steps (in the philosophy of replayable redux actions) as kind of "patches" applied after ejecting so they can be applied to a new version of create-react-app react-scripts without having to manually note them down and apply them. |
We had a discussion in #130. The conclusion was that they're not being entirely clear about which features are safe and which features aren't. If you can suggest a safe future-proof subset, happy to include it by default. But even custom properties aren't safe.
Not quite sure what you mean, but we'd allow whatever CSS Modules normally allows. For example https://github.com/css-modules/css-modules#composing-from-other-files.
And for those cases we ask you to file issues 😉 . We always asked people to share specific examples where our default rules don't work, and we're happy to consider changing them. Could you please copy paste your comment into a new issue and we can take it from there? |
I left a message over here: #4085 on a merged pull request. I've been testing react-scripts@next so I can use babel-plugin-macros with my react-apollo app, however this fix does not seem to be in 2.0. Is it possible to have this fix so we can use graphql in the alpha version of react-scripts? |
Please file a new issue? It’s hard to track conversation in merged PRs. |
Sorry if this is out of place, but are there any instructions for testing the latest code? I'd like to experiment with merge #4077 but not quite sure how it's meant to be tested without a release... |
@AndrewCraswell wait till maintainers announce a new tag. |
i notice that |
@geminiyellow No release was cut yet with merged in Webpack 4. It's merged in but not published yet. |
@strothj thank you. wating... |
@gaearon Would it be feasible to create a separate issue for release announcements only and lock comments to avoid notification noise? That’s all I’m interested in knowing about and could then unsubscribe from this issue. |
@detrohutt I recommend https://tellmewhenitcloses.com |
@pelotom thank you, but I was referring to the beta releases. I’m sure that will be adequate for some people though, so thanks for sharing. |
Hi int64go, I believe there will be another release to test webpack 4 integration. |
Blockers column: https://github.com/facebook/create-react-app/projects/3 |
I’ve locked the conversation to only include maintainers so that there is less notification noise for everybody else. I appreciate everyone’s impatience with this, but let’s respect people’s inboxes. :-) If you want to help out with maintenance please reach out in Twitter DMs. We still could use more help. (Especially in terms of driving project towards the 2.x release: not just feature development, but looking at the overall strategy, finding blockers and resolutions, planning and scoping features.) There’s a lot of work that’s already been done, but to me 2.0 still feels a bit out of reach, and I think we might want to scope it back a little bit and omit some things we originally planned. I feel like we should time 2.0 final around the same time Babel 7 goes stable, and if something doesn’t make the cut, it should go into 3.x instead. To all maintainers— please feel free to continue announcements and crucial 2.x related discussion on this thread. I only locked to avoid repetitive comments like “when does this come out”. It will come out when it’s ready, and if you want to help, you can reach out to me. |
Hello everyone! Sorry that it has been a while since our last alpha. We just released 📦 Here's what's inside:
Let us know if you run into any issues. 😄 note: to use the new browser defaults, remove the |
I just released |
The (hopefully) final beta is out. Please see #5103 for more details! |
We have just released
react-scripts@1.1.0
and, aside from critical vulnerabilities or similar issues, we intend this to be the last 1.x release. Our work on the 2.x release ofreact-scripts
is in thenext
branch, and we switched it to be the default on GitHub. This way people who automatically sync their forks withmaster
will only get non-breaking updates until thenext
branch is truly ready.Already Merged
So what’s gonna be in 2.x? Here’s a few big things that are already in the next branch:
node_modules
with Env Preset (Compile dependencies with babel-preset-env #3776)propTypes
definitions in the production build (Remove PropTypes from production build (#209) #3818)Very Likely to Land in 2.0 (But Might Need Your Help)
There are many more things we want to do but it will require help from the community. For now, they’re optimistically tagged with a
2.0.0
milestone (issues, PRs) but it’s likely we’ll only get to some of them. If you feel strongly about any of them, look at these issues, offer help if you’d like to increase their changes of getting landed, provide feedback to people who submit PRs, help them with planning and design, etc. What gets merged in the end really depends on your participation.I feel strongly that these are blockers that should get into 2.0:
node_modules
(Follow-up work for compiling node_modules #3777, needs PRs)They’re relatively fleshed out although Sass will need somebody to make a PR once other pieces are in place. We should also figure out a way to make Sass work with CSS Modules. We’ll also need a PR for making service workers opt-in.
Issues and PRs That Need More Work and Discussion
These look less fleshed out to me and might need more discussion, design, and implementation work:
Please Participate!
So, what do you think? Does this list look exciting to you? If you want to help, please participate. I don’t expect that I’ll have a ton of time to work on all of this personally, but we have a really great community and I hope you can help us flesh out these proposals. If you also want to help maintaining the project (and have some experience maintaining open source projects; not necessarily large ones) please also let us know.
☢️ How Can I Test This Now? ☢️
We're happy you'd like to test the next version of
react-scripts
! Before getting into the details, we'd like to make you aware of a few things:You can install the latest alpha version of
react-scripts
using one of the following commands:Known Issues in 2.x Alphas
None, currently.
Please report any other bugs you encounter or behavior you believe to be incorrect. Have fun!
The text was updated successfully, but these errors were encountered: