Open
Conversation
docs(next): refresh SVGR setup for Next.js (Webpack + Turbopack) and TS types - Add/clarify Next.js config examples for Webpack and Turbopack (13–15.3 +) - Fix wording/typos in the TypeScript section
|
@h-labushkina is attempting to deploy a commit to the Greg Berg's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the Next.js docs to clarify and modernize the SVGR setup across supported Next.js versions. This resolves ambiguity around Webpack vs. Turbopack configuration, documents classic ?url SVG imports, and adds TypeScript typings guidance (module declarations + tsconfig.json include ordering) to prevent missing type errors.
Test plan
Docs change only
Verified formatting/renders correctly by previewing the updated page at website/pages/docs/next.mdx in the docs site locally