From 3cdfae0e36913d5200b8b94f3f87a708d7af1664 Mon Sep 17 00:00:00 2001 From: jonniebigodes Date: Mon, 30 Sep 2024 18:55:11 +0100 Subject: [PATCH] Merge pull request #29245 from JavanPoirier/patch-1 Docs: NextJs framework fix viteFinal link (cherry picked from commit 8d0e714457632c397da6c41cb1d841a9a1c13c0a) --- docs/get-started/frameworks/nextjs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/get-started/frameworks/nextjs.mdx b/docs/get-started/frameworks/nextjs.mdx index 597522f03020..14e2c3e55294 100644 --- a/docs/get-started/frameworks/nextjs.mdx +++ b/docs/get-started/frameworks/nextjs.mdx @@ -107,7 +107,7 @@ Storybook for Next.js is a [framework](../../contribute/framework.mdx) that make {/* prettier-ignore-end */} - If your Storybook configuration contains custom Webpack operations in [`webpackFinal`](../../api/main-config/main-config-webpack-final.mdx), you will likely need to create equivalents in [`viteFinal`]((../../api/main-config/main-config-vite-final.mdx)). + If your Storybook configuration contains custom Webpack operations in [`webpackFinal`](../../api/main-config/main-config-webpack-final.mdx), you will likely need to create equivalents in [`viteFinal`](../../api/main-config/main-config-vite-final.mdx). Finally, if you were using Storybook plugins to integrate with Next.js, those are no longer necessary when using this framework and can be removed: