Configuring the output
configuration options tells webpack how to write the compiled files to disk. Note that, while there can be multiple entry
points, only one output
configuration is specified.
The minimum requirement for the output
property in your webpack configuration is to set its value to an object and provide an output.filename
to use for the output file(s):
webpack.config.js
module.exports = {
output: {
filename: 'bundle.js',
},
};
This configuration would output a single bundle.js
file into the dist
directory.
If your configuration creates more than a single "chunk" (as with multiple entry points or when using plugins like CommonsChunkPlugin), you should use substitutions to ensure that each file has a unique name.
module.exports = {
entry: {
app: './src/app.js',
search: './src/search.js',
},
output: {
filename: '[name].js',
path: __dirname + '/dist',
},
};
// writes to disk: ./dist/app.js, ./dist/search.js
Here's a more complicated example of using a CDN and hashes for assets:
config.js
module.exports = {
//...
output: {
path: '/home/proj/cdn/assets/[fullhash]',
publicPath: 'https://cdn.example.com/assets/[fullhash]/',
},
};
In cases where the eventual publicPath
of output files isn't known at compile time, it can be left blank and set dynamically at runtime via the __webpack_public_path__
variable in the entry point file:
__webpack_public_path__ = myRuntimePublicPath;
// rest of your application entry