# Next.js App Router Webpack SVG Sprite Quick Start This guide targets the exact mode key `next@app/webpack`: a generated typed React icon for the Next.js App Router and Webpack 5. ## 1. Generate the sprite No package installation and no `package.json` dependency are needed. `npx` downloads the CLI temporarily, and generated runtime does not import `@gromlab/svg-sprites`. Keep the config adjacent to its source icons: ```text src/ui/icons/ ├── icons/ │ ├── check.svg │ └── folder.svg └── svg-sprite.config.ts ``` Use a plain default object export with no package import: ```ts // src/ui/icons/svg-sprite.config.ts export default { mode: 'next@app/webpack', name: 'icons', } ``` When `input` is omitted, SVG files are read from `./icons` relative to the config. A `.js` config with a default export and a `.json` config are also supported. Generate directly with: ```bash npx --yes --package=@gromlab/svg-sprites@latest svg-sprites src/ui/icons/svg-sprite.config.ts ``` Generate once per invocation and keep the exact Webpack flags on both commands: ```json { "scripts": { "sprites": "npx --yes --package=@gromlab/svg-sprites@latest svg-sprites src/ui/icons/svg-sprite.config.ts", "dev": "npm run sprites && next dev --webpack", "build": "npm run sprites && next build --webpack" } } ``` Do not add `predev` or `prebuild` hooks to these scripts; that would run generation twice. In CI, replace `latest` with an exact package version. Generation creates a local `.gitignore`; commit that file once, but do not commit `.svg-sprite/`. Generated declarations are self-contained and do not require the package. ### Production usage The generated icon has no `'use client'` directive and is Server Component-compatible. Import it directly in an App Router page or layout: ```tsx // src/app/page.tsx import { IconsIcon, iconsIconNames, } from '../ui/icons/.svg-sprite/index.js' export default function Page() { return (

{iconsIconNames.length} icons available

) } ``` Webpack resolves the generated `new URL('../sprite.svg', import.meta.url)` and CSS Module, emitting a separate SVG asset. Keep the mode and the `--webpack` dev/build flags aligned. If custom Next.js webpack rules process SVG through SVGR, exclude `.svg-sprite/sprite.svg` from those rules. ## 2. Debug and preview This section is optional. Only users who need the Viewer or icon previews should install: ```bash npm install --save-dev @gromlab/svg-sprites ``` Viewer is interactive, so place the React bridge in a separate Client Component: ```tsx // src/app/icon-debug/IconsViewer.tsx 'use client' import { SpriteViewer } from '@gromlab/svg-sprites/react' const sources = [ () => import('../../ui/icons/.svg-sprite/svg-sprite.manifest.js'), ] export function IconsViewer() { return } ``` Render it from the route's Server Component: ```tsx // src/app/icon-debug/page.tsx import { IconsViewer } from './IconsViewer' export default function IconDebugPage() { return } ``` Keep the route internal or development-only. Viewer is not part of the production icon runtime. ## 3. Type the config Choose one of these two paths. ### With a local package installation After installing the package locally, use the helper: ```ts import { defineSpriteConfig } from '@gromlab/svg-sprites' export default defineSpriteConfig({ mode: 'next@app/webpack', name: 'icons', }) ``` You can alternatively import `type SpriteConfig` and apply `satisfies SpriteConfig`. ### Without the package Copy a mode-specific type directly into the config: ```ts type LocalSpriteConfig = { mode: 'next@app/webpack' name?: string description?: string input?: string | string[] transform?: { removeSize?: boolean replaceColors?: boolean addTransition?: boolean } generatedNotice?: boolean } export default { mode: 'next@app/webpack', name: 'icons', } satisfies LocalSpriteConfig ```