npm / @svgr/webpack
@svgr/webpack
What changed in @svgr/webpack 5 to 8, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-25.
7 breaking8 new APIs and options1 behavior and defaults4 tooling3 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@svgr/webpack 84 changes
Breaking changes 1
The index template now receives an array of objects containing the created component path and the original SVG path.
New APIs and options 1
Adds a snake_case filename option.
Tooling 1
Generated code changes SVGProps from a regular import to an import type.
Fixes and other changes 1
Fixes a parseObject error that caused the website to break.
@svgr/webpack 73 changes
Breaking changes 2
SVGR now requires Node.js v14 or later.
plugin-jsx is no longer included by default in core.
New APIs and options 1
You can now specify jsxRuntimeImport in the configuration.
@svgr/webpack 611 changes
Breaking changes 2
The SVGO config format changes, and SVGR no longer merges SVGO config.
The template format changes.
New APIs and options 4
An option was added to explicitly use named exports.
Icon size can be specified.
An index option was added.
JSX runtime selection is supported.
Behavior and default changes 1
CSS variables are supported.
Tooling 2
TypeScript declarations were added to @svgr/core.
A webpack TypeScript preset configuration was added.
Fixes and other changes 2
The mask-type property is supported.
Webpack 5 behavior with url-loader was fixed.
@svgr/webpack 55 changes
Breaking changes 2
Changes the default template to use a function.
Node.js v8 is no longer supported.
New APIs and options 2
Adds the memo option.
Adds a titleId prop to enhance accessibility.
Tooling 1
Adds support for file-loader v5.