Which directory contains assets that will be served directly without additional processing by webpack?

Which directory contains assets that will be served directly without additional processing by webpack?

• A. public
• B. src
• C. build
• D. assets

Answer: (A)

Assets that you want to serve directly without any bundling or transformation belong in the public directory. Files here are not processed by webpack; they’re served by the development server or copied to the output as-is, so you can reference them by their root paths (for example, /logo.png or /images/banner.jpg). This makes public ideal for static resources like images, icons, or the app’s index.html. In contrast, files placed in the source directory are meant to be part of the module graph and are processed by webpack, often through loaders, and end up in the bundled output. The build directory is simply where the final, production-ready bundles live after the build process. An assets folder doesn’t have a special meaning to webpack unless you configure it—so it won’t be automatically served without processing.

Assets that you want to serve directly without any bundling or transformation belong in the public directory. Files here are not processed by webpack; they’re served by the development server or copied to the output as-is, so you can reference them by their root paths (for example, /logo.png or /images/banner.jpg). This makes public ideal for static resources like images, icons, or the app’s index.html.

In contrast, files placed in the source directory are meant to be part of the module graph and are processed by webpack, often through loaders, and end up in the bundled output. The build directory is simply where the final, production-ready bundles live after the build process. An assets folder doesn’t have a special meaning to webpack unless you configure it—so it won’t be automatically served without processing.