From 2a3ac8da4d723bfd9e0e42afc0d99cf693da22f6 Mon Sep 17 00:00:00 2001 From: ZeeshanTamboli Date: Tue, 17 Sep 2024 11:40:19 +0530 Subject: [PATCH] add note about Next.js --- .../guides/minimizing-bundle-size/minimizing-bundle-size.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/data/material/guides/minimizing-bundle-size/minimizing-bundle-size.md b/docs/data/material/guides/minimizing-bundle-size/minimizing-bundle-size.md index cfa6e48cb39576..bd564dec4452aa 100644 --- a/docs/data/material/guides/minimizing-bundle-size/minimizing-bundle-size.md +++ b/docs/data/material/guides/minimizing-bundle-size/minimizing-bundle-size.md @@ -100,7 +100,7 @@ If you're using ESLint you can catch problematic imports with the [`no-restricte ### Option two: use a Babel plugin -This option provides the best user experience and developer experience: +This option provides the best user experience and developer experience, except if you're using **Next.js 13.5 or greater**, where this optimization is automatically applied via the `optimizePackageImports` option in Next.js. In that case, using a Babel plugin is unnecessary. - UX: The Babel plugin enables top-level tree-shaking even if your bundler doesn't support it. - DX: The Babel plugin makes startup time in dev mode as fast as Option 1.