v4.0.0
SVGO v4.0.0
Breaking Changes
- Node.js v14 support dropped — v16+ required
removeViewBoxandremoveTitledisabled by default — re-enable in config if needed; they reduce scalability and accessibility respectively
Unclaimed project
Are you a maintainer of svgo? Claim this project to take control of your public changelog and roadmap.
The library for web and native user interfaces.
The React Framework
Complete Claude Code configuration collection - agents, skills, hooks, commands, rules, MCPs. Battle-tested configs from an Anthropic hackathon winner.
Coding articles to level up your development skills
removeViewBox and removeTitle disabled by default — re-enable in config if needed; they reduce scalability and accessibility respectivelyremoveScriptElement renamed to removeScripts — update config referencessvgo/dist/svgo.browser.js → svgo/browsersvgo/lib/builtin → top-level builtinPlugins exportbuiltinPlugins array instead of direct pathsquerySelectorAll, querySelector, matches) lose tree context by default — pass rootNode as 3rd argument if selector traverses parent/sibling nodes; use mapNodesToParents() helper to ease migrationXastNode#parentNode removed — internal refactor for custom plugins using tree traversalVERSION export for runtime version detectionisPreset and plugins properties on preset pluginsremoveDeprecatedAttrs plugin (disabled by default) to strip deprecated SVG attributesremoveEditorsNSData now removes Boxy SVG and Krita namespacesconvertColors converts all color references (except IDs) to lowercase by default; configurable via convertCasecleanupIds: handle URI-encoded and non-URI-encoded IDs consistentlycollapseGroups: check styles + attributes; move attributes atomicallyconvertPathData: fix q control point removal; preserve vertex for marker-only pathsmergePaths: don't merge if attributes/styles depend on bounding boxmoveElemsAttrsToGroups: skip transforms when group has filter attributeprefixIds: handle XML comments in style tags correctlyremoveEmptyContainers: preserve containers with CSS-applied filtersremoveHiddenElems: respect referenced IDs; treat path[opacity=0] as non-renderingremoveUselessDefs: preserve nodes with IDsDefault preset now slightly larger (Arch Linux: +0.018 KiB, Isometric: -0.441 KiB) due to disabled removeViewBox/removeTitle. Browser bundle: +27.2 kB.
Illustration by Vukory
It's been just over a year since our first release candidate, but I believe we can now release SVGO v4.0.0 with confidence! Thank you to all contributors who tested our RC builds and reported issues back up, this really smoothed out the process.
We actually wanted to do the release sooner, but it was a challenge to find the right time to publish a major release, since that means setting time aside to support users through migrations, helping downstream projects migrate, being available to fix or document things that users found to have an unexpected impact by this release, etc. I appreciate everyone's patience, and now that this is done, we can hopefully increase the pace of development again and tackle that backlog of old bugs. ^-^'
Please refer to the Migration Guide from v3 to v4 for a more concise version! This section is more verbose as it delves into the motivation of changes too.
Node.js v14 is no longer supported by the Node.js team, including security support, since 30 April 2023. Node.js v16 is no longer supported either, but as some are still using it, we'll save dropping support for Node.js v16 for the next major release.
This allows us to update our dependencies to more recent versions and to access more modern Node.js APIs.
Node.js v14 may still work at the time of this release, but we'll no longer be testing against v14 from now on.
Both removeViewBox and removeTitle have been disabled by default. Both have been major pain points for users and don't make sense to enable in most cases. Other libraries wrapping SVGO have also been disabling these plugins by default, such as Docusaurus and SVGR.
If you would like either of these plugins enabled, you can do so by configuring it in the SVGO config, see the README for more context, however please read the warnings described in the documentation of the plugins first:
export default {
plugins: [
'preset-default', // built-in plugins enabled by default
+ 'removeViewBox',
+ 'removeTitle',
],
};
The removeScriptElement plugin has been renamed to removeScripts, to more accurately reflect what the plugin does. It does not only remove the <script> tag, but also event handlers and script URIs from links.
To migrate, amend your SVGO config to refer to removeScripts instead if you use that plugin.
export default {
plugins: [
'preset-default', // built-in plugins enabled by default
- 'removeScriptElement',
+ 'removeScripts',
],
};
We now enforce boundaries between the intended public API and any internal structures/helpers. This is the biggest change in SVGO's JavaScript API and will enable maintainers and users to have a mutual understanding of what is public API and what isn't.
There are two ways to import SVGO:
svgo — for normal usage, such as scripts or server-side applications.svgo/browser — for browser usage.If you use the browser bundle, you must amend how you import SVGO:
- import { optimize } from 'svgo/dist/svgo.browser.js';
+ import { optimize } from 'svgo/browser';
For ESM/browser, you must use named imports:
// ESM and Browser, named exports
import { VERSION } from 'svgo';
console.log(VERSION); // 4.0.0-rc.0
// ESM and Browser, import all
import * as svgo from 'svgo/browser';
console.log(svgo.VERSION); // 4.0.0-rc.0
// Common JS, default export
const svgo = require('svgo');
console.log(svgo.VERSION); // 4.0.0-rc.0
// CommonJS, named exports
const { VERSION } = require('svgo');
console.log(VERSION); // 4.0.0-rc.0
We support 3 environments, ESM, Common JS, and browser. The only functional difference is that the loadConfig function is not exported in the browser bundle.
If you depended on a helper that we haven't declared as public, then you are encouraged to implement it yourself, or dig into our source and copy it over to your project.
If you import/require the array of built-in plugins, or a single plugin during runtime, this is now a top-level export instead:
// builtin.mjs - get an array of all built-in plugins
- import { builtin } from 'svgo/lib/builtin';
+ import { builtinPlugins } from 'svgo'
// plugin.mjs - get a single plugin
- import presetDefault from 'svgo/plugins/preset-default';
+ import { builtinPlugins } from 'svgo';
+ const prefixDefault = builtinPlugins.find(plugin => plugin.name === 'preset-default');
// plugin-map.mjs - get all plugins as a map using the plugin name as a key
import { builtinPlugins } from 'svgo';
const pluginMap = builtinPlugins.reduce((acc, val) => acc.set(val.name, val), new Map());
The XastNode#parentNode property was declared legacy and pending removal for v4, but was still used internally. The remaining instances have now been removed, which required a refactor of the selector helpers.
This effects custom plugins that use any of the following functions, where the selector (2nd) argument could reference parent or sibling nodes (i.e. div > span):
querySelectorAllquerySelectormatchesPreviously, these functions had the context of the whole node tree, even if a child node was passed to it. It no longer has that context by default. The new API for these functions is as follows:
// applies `selector` with the context of the `childNode` and its descendants
const nodes = querySelectorAll(childNode, selector);
// applies `selector` with the context of the entire node tree relative from `childNode`
// the `rootNode` is required if the result of `selector` may depend on the parent or sibling of `childNode`
const nodes = querySelectorAll(childNode, selector, rootNode);
// this usage has the same behavior as v3, as `rootNode` is already the entire node tree
const nodes = querySelectorAll(rootNode, selector);
A helper has been provided named #mapNodesToParents, which does this for you. This can be used to easily migrate to the new API. If you're not sure if you need it, then it's safer to take this approach. The third argument won't be necessary if selector does not traverse nodes, for example, querying using one or more attributes of a single node.
- import { querySelectorAll } from 'svgo';
+ import { querySelectorAll, mapNodesToParents } from 'svgo';
- const nodes = querySelectorAll(childNode, selector);
+ const nodes = querySelectorAll(childNode, selector, mapNodesToParents(rootNode));
SVGO is now a dual package, serving for both Common JS and ESM usage. To be more explicit, SVGO will continue to work on Common JS projects!
Thanks to @jdufresne for doing the bulk of the work.
convertCase to false.filter attribute. By @johnkenny54 in #1933path[opacity=0] as a non-rendering node. By @johnkenny54 in #1948-o argument) ends with a trailing slash to a location that didn't exist. By @SethFalco in #1954VERSION export so get the version of SVGO during runtime. By @SethFalco in #2016isPreset and plugins property to plugins, which are only defined for presets. This will indicate if the plugin is a preset, and return the plugins that are in the preset in the order they are invoked.Before and after using vectors from various sources, with the default preset of each respective version:
| SVG | Original | v3.3.2 | v4.0.0 | Delta | |---|---|---|---|---| | Arch Linux Logo | 9.529 KiB | 4.115 KiB | 4.097 KiB | ⬇️ 0.018 KiB | | Blobs | 50.45 KiB | 42.623 KiB | 42.633 KiB | ⬆️ 0.01 KiB | | Isometric Madness | 869.034 KiB | 540.582 KiB | 540.141 KiB | ⬇️ 0.441 KiB | | tldr-pages Banner | 2.071 KiB | 1.07 KiB | 1.07 KiB | | | Wikipedia Logo | 161.551 KiB | 111.668 KiB | 111.727 KiB | ⬆️ 0.059 KiB |
Note: The increase in size from previous versions is from disabling removeViewBox and removeTitle, with the benefit of preserving scalability and accessibility.
Before and after of the browser bundle of each respective version:
| | v3.3.2 | v4.0.0 | Delta | |---|---|---|---| | svgo.browser.js | 753.0 kB | 780.2kB | ⬆️ 27.2 kB |