Skip to content
DocsErrorsSWC Failed to Load

SWC Failed to Load

Why This Message Occurred

Next.js now uses Rust-based compiler SWC to compile JavaScript/TypeScript. This new compiler is up to 17x faster than Babel when compiling individual files and up to 5x faster Fast Refresh.

SWC requires a binary to be downloaded that is compatible with your system. In some cases this binary may fail to load either from failing to download or an incompatibility with your architecture.

Possible Ways to Fix It

When on an M1 Mac and switching from a Node.js version without M1 support to one with, e.g. v14 to v16, you may need a different swc dependency which can require re-installing node_modules (npm i --force or yarn install --force).

On Windows make sure you have Microsoft Visual C++ Redistributable installed.

Alternatively, you might need to allow optional packages to be installed by your package manager (remove --no-optional flag) for the package to download correctly.

In some cases your package manager (e.g. npm) might have generated a lockfile that only includes optionalDependencies specific to the platform it was generated on, preventing the optionalDependency needed for CI from being installed.

This can be fixed by removing the lockfile and regenerating it with a newer version of your package manager npm i -g npm@latest.

If SWC continues to fail to load you can opt-out by disabling swcMinify in your next.config.js or by adding a .babelrc to your project with the following content:

  "presets": ["next/babel"]

Be sure to report the issue on the feedback thread so that we can investigate it further.