Note: changes to webpack config are not covered by semver so proceed at your own risk
Before continuing to add custom webpack configuration to your application make sure Next.js doesn't already support your use-case:
Some commonly asked for features are available as plugins:
In order to extend our usage of webpack, you can define a function that extends its config inside next.config.js, like so:
module.exports = { webpack: ( config, { buildId, dev, isServer, defaultLoaders, nextRuntime, webpack } ) => { // Important: return the modified config return config }, }
The
webpackfunction is executed twice, once for the server and once for the client. This allows you to distinguish between client and server configuration using theisServerproperty.
The second argument to the webpack function is an object with the following properties:
buildId: String - The build id, used as a unique identifier between buildsdev: Boolean - Indicates if the compilation will be done in developmentisServer: Boolean - It's true for server-side compilation, and false for client-side compilationnextRuntime: String | undefined - The target runtime for server-side compilation; either "edge" or "nodejs", it's undefined for client-side compilation.defaultLoaders: Object - Default loaders used internally by Next.js:
babel: Object - Default babel-loader configurationExample usage of defaultLoaders.babel:
// Example config for adding a loader that depends on babel-loader // This source was taken from the @next/mdx plugin source: // https://github.com/vercel/next.js/tree/canary/packages/next-mdx module.exports = { webpack: (config, options) => { config.module.rules.push({ test: /\.mdx/, use: [ options.defaultLoaders.babel, { loader: '@mdx-js/loader', options: pluginOptions.options, }, ], }) return config }, }
nextRuntimeNotice that isServer is true when nextRuntime is "edge" or "nodejs", nextRuntime "edge" is currently for middleware and server components in edge runtime only.