score:251

Accepted answer

create-react-app encapsulates all of the npm modules it is using internally, so that your package.json will be very clean and simple without you having to worry about it.

However, if you want to start doing more complex things and installing modules that may interact with modules create-react-app is using under the hood, those new modules need to know what is available and not, meaning you need to have create-react-app un-abstract them.

That, in essence, is what react-scripts eject does. It will stop hiding what it's got installed under the hood and instead eject those things into your project's package.json for everyone to see.

score:3

react-scripts basically encapsulates all the configurations and boilerplate in a single dependency so you won't have to configure the complete project from scratch. However, there might be a case where you want to override those configurations for build customization or something more specific. hence, it provides eject functionality so you can take control over those configurations. Including lint, bundling, code-splitting, etc.

score:4

There are packages that will allow customizing without ejecting, acting like a middleware between react-scripts and your customizations:

score:5

eject: is an advanced operation it allows you to customize the configuration under Create-React-App(react-scripts)

Before do eject you need to understand the consequences: it is a one-way operation!

The only reason I would encourage you to do eject is that: learn how the build process(create-react-app) works.

One more thing you need to do before eject is to commit your project to git. If your current project hasn't been added to git yet. npm run eject or yarn eject will fail.

score:115

npm run eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

link to documentation


Alternatives to Ejecting

Ejecting lets you customize anything, but from that point on you have to maintain the configuration and scripts yourself. This can be daunting if you have many similar projects. In such cases instead of ejecting we recommend to fork react-scripts and any other packages you need. This article dives into how to do it in depth. You can find more discussion in this issue.


Related Query

More Query from same tag