[evoactivity]

A custom svgo config replaces the baseline config. The README options and the SvgJarOptions comment said it was deep-merged, which was wrong.

What changed

• baselineSvgoConfig is exported from @svg-jar/plugin. To keep the baseline and add plugins, copy its plugins into a custom config:

  import { baselineSvgoConfig } from '@svg-jar/plugin';
  
  svgJar({ svgo: { plugins: [...baselineSvgoConfig.plugins, 'removeDimensions'] } });

• The export is frozen, and its plugins list is typed as read-only, so one caller cannot change the default for every build.

• The README and SvgJarOptions docs now say a custom config replaces the baseline. The README also explains why a config written without the baseline should keep the cleanupIds override, because shortened IDs from different files can collide in one sprite sheet.

The baseline is not merged automatically. With a merge, users could not remove baseline plugins, and changing a baseline setting would run preset-default twice.

Tests

Unit tests check that the export matches the svgo: true behaviour, that it can be extended, that it cannot be changed, and that a custom config is used without the baseline.

🤖 Generated with Claude Code