Which command bundles the app into static files for production?

Which command bundles the app into static files for production?

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

Answer: (B)

Bundling for production means turning your app into optimized static assets that can be served efficiently by a static host. In a typical React setup, you trigger that process with a dedicated build script. Running that build command compiles and bundles your code, producing a set of static files placed in a build/ directory. These assets include a minified JavaScript bundle, CSS, and other assets, often with hashed filenames to improve caching. The result is ready-to-serve production files. Other commands serve different purposes: starting the development server provides a fast, live-reload environment and doesn’t produce production bundles; running tests executes your test suite; eject exposes the underlying configuration but doesn’t itself create the production bundle. So, the command that bundles the app into static files for production is npm run build.

Bundling for production means turning your app into optimized static assets that can be served efficiently by a static host. In a typical React setup, you trigger that process with a dedicated build script. Running that build command compiles and bundles your code, producing a set of static files placed in a build/ directory. These assets include a minified JavaScript bundle, CSS, and other assets, often with hashed filenames to improve caching. The result is ready-to-serve production files.

Other commands serve different purposes: starting the development server provides a fast, live-reload environment and doesn’t produce production bundles; running tests executes your test suite; eject exposes the underlying configuration but doesn’t itself create the production bundle.

So, the command that bundles the app into static files for production is npm run build.