Which command ejects the app and copies build dependencies and configuration into the app directory (and you can't go back)?

Which command ejects the app and copies build dependencies and configuration into the app directory (and you can't go back)?

• A. npm start
• B. npm run build
• C. npm test
• D. npm run eject

Answer: (D)

Ejecting a CRA app exposes and copies all the build tooling and configuration into your project, giving you full control over how the app is built and run. Running this command starts that process: it copies webpack, Babel, ESLint, and other build dependencies and their configuration into your project, updates package.json and related config files, and removes the single react-scripts dependency so you manage everything locally. Once you eject, you can’t easily revert to the original managed setup. The other common commands are for development and production workflows but do not copy or move the build configuration into your project. They run the dev server, create a production bundle, or run tests using the existing CRA setup.

Ejecting a CRA app exposes and copies all the build tooling and configuration into your project, giving you full control over how the app is built and run. Running this command starts that process: it copies webpack, Babel, ESLint, and other build dependencies and their configuration into your project, updates package.json and related config files, and removes the single react-scripts dependency so you manage everything locally. Once you eject, you can’t easily revert to the original managed setup.

The other common commands are for development and production workflows but do not copy or move the build configuration into your project. They run the dev server, create a production bundle, or run tests using the existing CRA setup.