-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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 version 3.3.0 #7981
Comments
I just tried it out this morning and it looks like the patch for the I nuked my react-scripts directory in node_modules before reinstalling as a user over there cited caching issues. Thanks CRA contributors et al. for all you do! You make work extra enjoyable. |
hey, guys. appreciate the great work! what is the best way to get TS 3.7 working on my existing project right now? i am not particularly interested in templates and would think a 3.3.0 with just the upgrade to TS 3.7 would've been great in case templates are preventing the release somehow. |
Actually TypeScript 3.7 and the required changes in typscript-eslint and Prettier were blocking the release. I believe the final typescript-eslint fixes have been published so we're hoping to release 3.3.0 in the next couple of days. |
typscript-eslint and Prettier now officially support TS 3.7, right? Any further blockers to release CRA 3.3 (maybe just with TS 3.7 support and deferring all the unfinished stuff)? |
yeah, I mean I appreciate what cra does so much and I refuse to eject over this, but TS 3.7 and it's features are something I think a lot of people have wanted/needed for quite a while and I think the team here doesn't appreciate that. they need to be more vocal about what the hold up is or just release already, please. |
If you want them to just release I don't think the team at FB needs to do anything differently. This project is fantastic. It's free work that we all benefit from. They have internal needs that are vastly more complex than most of our needs. |
My reason for not using @next is I'm not working on a hobby project, mostly. I kinda find using alpha or beta stuff in production kind of a big deal. |
How do you update an existing project to use it? I created a new one using the steps above and see that the only difference is |
@rhyek - Well, if you don't want to use alpha or beta stuff in production, then maybe you should stop demanding that they release alpha or beta stuff to production? Seems pretty simple to me - if you think it's ready to release, then go ahead and use it. If not, wait until they're done - because otherwise you're demanding that they do a bunch of free work for you right now in order to make it ready for release. Anyway, |
@waynebloss appreciate your input. as I understand it, all blockers from dependencies have been resolved and TS 3.7 was released nearly a month ago, so I don't understand what is holding the release back. maybe there is an issue someone from the community could help with. i would love to contribute, although i haven't looked at the project's source code. i personally don't understand what using @next implies and what to watch out for, so won't personally opt into that. i feel you are being overly defensive and I don't have anything else to add here, so hopefully we see a release soon. |
@JoshClose I started a new project to try it out, using the instructions at the top of this post. Maybe you can try that and compare the result to your project. @rhyek I apologize if I came off as overly defensive. The CRA team has made my life so much easier that I feel the need to defend them. Also, it's Monday morning so maybe I'm just a little more cranky than usual xD - Hope you have a great rest of the day. |
If the maintainers aren't typescript users they probably just aren't aching for the update the way we are. One of the tradeoffs in using CRA is that sometimes you have to wait longer for new features, especially if those features aren't as important to the maintainers/core team as they are to you. This is free software, we're all free to make our own webpack configs, or eject, or fork the project, etc. |
@JoshClose Your investigation was correct, to use it in an existing project, update your package dependencies to use Thanks CRA team for your work on this! I'd be curious if you're working towards a more complete 3.3 with issues from the milestone, or if there are blockers you're waiting for a resolution for, such as typescript-eslint/typescript-eslint#1051. |
Would love to see another Our team, in particular, would like to test out the fixes introduced in #7988, but there have been many other PRs too. |
@ayush987goyal are you sure this is up to date? I just find it strange that two weeks ago they said the release should be "in the next couple days". |
Please dont be demanding, the team is probably developing this in their own free time and they dont owe any of us anything. Anyone is free to fork this project. Your node_modules is also your code, it’s not a magic black box that you can’t touch |
I’ll just mention Create React App is maintained by a team of volunteers rather than by Facebook. (We are very busy with React itself at this moment.) Being excessively demanding in threads like this is a textbook example of how to get these contributors to burn out. Then there won’t be nobody to do these releases at all. The right question is always “how can I help”. |
We are planning to release Create React App version 3.3.0 soon.
Planned Features
Refer to the 3.3.0 Milestone to see exactly what is included in this release.
☢️ 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:master
for how they're expected to workYou can install the latest beta version of
react-scripts
using one of the following commands:Known Issues in 3.3.0 Betas
no-restricted-globals
rule: false positive with optional chaining: [no-restricted-globals] False positive with optional chaining typescript-eslint/typescript-eslint#1090typescript-eslint
that don't yet support optional chaining: Support Optional Chaining in Rules typescript-eslint/typescript-eslint#1051Please report any bugs you encounter or behavior you believe to be incorrect by creating a new issue. Have fun!
The text was updated successfully, but these errors were encountered: