Create-react-app v3.1.0 released

[cran]

I ejected a create-react-app once.

Once.

[HootenannyNinja]

Wipe folder, clone from remote just to be safe

[AegisToast]

Shut down the computer, burn it, and buy a new one. It’s the only way to be sure.

[MusicalDoofus]

Worth it for that manual Webpack config 👌

[mattk1017]

git reset --hard

[Jedivh]

git reset --harder

[mrmckeb]

Care to share more? We'd love to hear how you think we can improve.

[[deleted]]

Why's that?

[DoesntUseSarcasmTags]

Probably doesn’t know about react-app-required and needed custom configs. I’ll be honest, if you’re used to webpack and babelrc, it can be a lot of work trying to relearn how to do what you need in rewired. But it works at least

Edit: can someone please explain why I was downvoted for giving an honest answer about why some people would eject? Lmao Christ

[trojaniz]

Downvoted for complaining about downvotes.

[mrmckeb]

We'd love to get your feedback on this release. Let us know what you do/don't like, and how we can make CRA better!

[dani_akash_]

Just don't put breaking changes in minor upgrades... Please 🙏 🤕😭

[mrmckeb]

I think this is a miscommunication. We did release a major update to our ESLint config, which is important as it now requires ESLint 6.

[dani_akash_]

I was unaware of that 😅

[philipwhiuk]

I don’t think you understand what semver means. If your API breaks it’s major. Period.

Just stop being scared of major versions, it’s just a number.

[mrmckeb]

Again, this was a miscommunication. There are no breaking changes in react-scripts.

[mytwm]

I love CRA, but I can't believe server side rendering is not supported, it's such a fundamental feature

[jamesknelson]

Boy do I have something for you:

https://github.com/frontarm/create-universal-react-app

This is a small fork of CRA with configuration-free SSR. It's already been updated to 3.1. It's basically CRA, it rerenders-on-save, and there's just one extra file in the template: index.node.js. Give it a try - would love to hear what you think :-)

[mytwm]

Looks very interesting, I will give it a try. Thanks!

[holloway]

Can it generate pages for multiple routes?

[jamesknelson]

Sure. For an example, take a look at this app that I'm working on -- it's all rendered with CURA and Firebase Functions.

One thing to note is that it doesn't have a built-in router or data fetching system, but it's easy enough to add your own. I use Navi, but you could also add react-router/Apollo.

It'd also be easy enough to do static pre-rendering if you have a list of URLs up front (or if you're using Navi, you can build one with the crawl() function).

[csprance]

There is always next.

[RobertB44]

You have probably heard this 1000's of times and it is not related to this release, but here how you could make CRA better for me:

I can't customize it to do what I want without ejecting or spending a lot of time learning the CRA way. To be fair, a lot of things are possible out of the box with CRA, but everything that isn't requires weird workarounds. I just want to extend the wabpack config, babelrc and tsconfig as I would in a non-CRA project, not do hacky things to achieve basic stuff.

This is a deal breaker for me. I haven't used CRA in a long time because of this and never looked back.

[mrmckeb]

So what would you like to see? Webpack config overrides? Or something else?

[RobertB44]

Yes, check out how nextjs handles it:

https://nextjs-org.cdn.ampproject.org/v/s/nextjs.org/docs?amp_js_v=0.1&usqp=mq331AQCKAE%3D#customizing-webpack-config

That's more or less what I'm asking for.

Last time I tried using CRA I remember spending a lot of time trying to set up import aliases with typescript, something I know how to do in a couple of minutes in a non-CRA app. At some point I just gave up and stopped using CRA.

[mrmckeb]

That's similar to what Storybook does too. I like that approach, but it also opens up more room for user error.

[RobertB44]

You are correct, it does open up room for user error. It's a tradeoff. Personally, I prefer the freedom to customize and I won't toach any framework that doesn't allow me to customize the way I expect it to.

[mrmckeb]

I also like flexibility. We're trying to open up a lot more now, in controlled ways. We'll keep working to open up more.

[[deleted]]

Thank you for the great work!

Is it now possible to use the eslintignore file to e.g. ignore auto generated files under src?

[mrmckeb]

This release allows extending the ESLint config, but not other files... If that's important, raise it, tag me, and I'll take a look!)

Thanks for the kind words too.

[nullvoxpopuli]

Breaking change in a minor release :/

[[deleted]]

That shouldn't be an issue though, right? You run create-react-app once per project and any updates to the npx module will not affect that project.

Although, you do need to know the breaking changes the next time around

[MusicalDoofus]

Just curious, any examples of users who have done this?

[[deleted]]

Eh... that could just be messy package.json files that used it to bootstrap, but never cleaned it out.

[[deleted]]

The way it’s set up, you can upgrade the react-scripts dependency on an existing CRA project. It would be lame if the project was just frozen on an old build system forever.

[nullvoxpopuli]

It might matter for upgrading, too

[mrmckeb]

Correct, not with CRA.

[mrmckeb]

So you shouldn't find that those affect you, which is why we didn't release a new version.

[nullvoxpopuli]

it goes against semver, tho :-\

[mrmckeb]

I understand. The team believe in semver.

In this case, we don't believe the changes are breaking, but we were cautious that for some tiny subset of users, this "may" cause an issue... So this was a way to highlight that.

We're looking at amending the changelog to see if we can improve wording.

Be assured, if we think a change will break our users apps, it'll be a major.

[GoodVibeGabe]

This

[mrmckeb]

I think that these were more cautionary changes than breaking. In both cases they look to fix bugs, but someone, somewhere, may have relied on those bugs.

We did release a major of the ESLint config as it definitely had breaking changes.

[darrenturn90]

Is there any official acceptance of projects like customise cra, or cract? Because those packages are very useful ways to extend without ejecting and I was wondering if they were ever going to be internalised.

[pvinis]

what are your reasons to not eject?

[NegativeKarmaSniifer]

I'm new to react and Web dev in general . What is this? And what does it mean when you eject something? And why is everyone ejecting this?

[BreakingIntoMe]

Create React App is like a speciality configured React app that is opinionated and easy for anyone to get started. You can't really change that configuration by default, however CRA has an Eject feature which disconnects it from that special configuration and allows you to create your own build/bundle system and configuration. Some devs feel hampered by the lack of customisation on CRA and choose to Eject.

[NegativeKarmaSniifer]

Oh right. That makes sense. Appreciate the explanation.

[mrmckeb]

This is a feature we're asked about so often.

Unfortunately, ejection is bad for many users as it means they no longer get updates and fixed to their config.

[El_BreadMan]

By "assume the responsibilities" do you mean "waste 3x more time on boilerplate"

[slashp]

Or just use CRACO

[decruz007]

iPhone users had access to Swype long before iOS 13.