From ae9c74cac07136b9ac2fcaf45a60cd57470e6eb9 Mon Sep 17 00:00:00 2001 From: ytori Date: Thu, 17 Oct 2024 17:07:40 +0900 Subject: [PATCH] fix broken link --- docs/04-architecture/turbopack.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/04-architecture/turbopack.mdx b/docs/04-architecture/turbopack.mdx index 7d52e4e92e863..d0f6a116db99b 100644 --- a/docs/04-architecture/turbopack.mdx +++ b/docs/04-architecture/turbopack.mdx @@ -43,7 +43,7 @@ These features are currently not supported: - A subset of [Webpack loaders](/docs/app/api-reference/next-config-js/turbo#configuring-webpack-loaders) are supported in Turbopack. - Babel (`.babelrc`) - Turbopack leverages the [SWC](/docs/architecture/nextjs-compiler#why-swc) compiler for all transpilation and optimizations. This means that Babel is not included by default. - - If you have a `.babelrc` file, you might no longer need it because Next.js includes common Babel plugins as SWC transforms that can be enabled. You can read more about this in the [compiler documentation](docs/architecture/nextjs-compiler#supported-features). + - If you have a `.babelrc` file, you might no longer need it because Next.js includes common Babel plugins as SWC transforms that can be enabled. You can read more about this in the [compiler documentation](/docs/architecture/nextjs-compiler#supported-features). - If you still need to use Babel after verifying your particular use case is not covered, you can leverage Turbopack's [support for custom webpack loaders](/docs/app/api-reference/next-config-js/turbo#configuring-webpack-loaders) to include `babel-loader`. - Creating a root layout automatically in App Router. - This behavior is currently not supported since it changes input files, instead, an error will be shown for you to manually add a root layout in the desired location.