Skip to content

Custom Webpack Config

Good to know: 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: (
    { buildId, dev, isServer, defaultLoaders, nextRuntime, webpack }
  ) => {
    // Important: return the modified config
    return config

The webpack function is executed three times, twice for the server (nodejs / edge runtime) and once for the client. This allows you to distinguish between client and server configuration using the isServer property.

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 builds
  • dev: Boolean - Indicates if the compilation will be done in development
  • isServer: Boolean - It's true for server-side compilation, and false for client-side compilation
  • nextRuntime: 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 configuration

Example 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:
module.exports = {
  webpack: (config, options) => {
      test: /\.mdx/,
      use: [
          loader: '@mdx-js/loader',
          options: pluginOptions.options,
    return config


Notice that isServer is true when nextRuntime is "edge" or "nodejs", nextRuntime "edge" is currently for middleware and Server Components in edge runtime only.