What is a key consequence of ejecting in the setup?

What is a key consequence of ejecting in the setup?

• A. It updates dependencies to the latest versions.
• B. It copies build dependencies and configuration into the project and cannot be easily undone.
• C. It starts the production server.
• D. It removes the build tooling entirely.

Answer: (B)

Ejecting makes the project take full control of its build setup by copying the build tooling and configuration into the repository. You end up with the actual build dependencies and all the configuration files (like webpack, Babel, ESLint, etc.) inside your project, rather than relying on a separate abstraction. This gives you complete customization power, but it’s effectively hard to revert because that original, managed setup is removed and you now maintain everything yourself. It’s not about updating dependencies automatically, starting a production server, or removing tooling—it’s about embedding and taking ownership of the build system itself.

Ejecting makes the project take full control of its build setup by copying the build tooling and configuration into the repository. You end up with the actual build dependencies and all the configuration files (like webpack, Babel, ESLint, etc.) inside your project, rather than relying on a separate abstraction. This gives you complete customization power, but it’s effectively hard to revert because that original, managed setup is removed and you now maintain everything yourself. It’s not about updating dependencies automatically, starting a production server, or removing tooling—it’s about embedding and taking ownership of the build system itself.