v3.0.0: migrate to TypeScript, svgo 4, and ESM; require Node 22.18+ #26
No reviewers
Labels
No labels
bug
dependencies
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
repos/gulp-svgo!26
Loading…
Reference in a new issue
No description provided.
Delete branch "release/v3.0.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Major release, stacked on the v2.3.0 PR.
preset-default+overrides;cleanupIDs→cleanupIds); optimized output differs from svgo 1.x.nodenext) compiled todist/with declarations;svgois the exported identifier.require('gulp-svgo')keeps returning the plugin function directly via the'module.exports'named export andrequire(esm). Both paths are covered by tests against the built artifact.Error(svgo error ascause) instead of passing through.node:test(15 tests incl. dist interop, multi-file ordering, invalid-config), oxlint + oxfmt, CI on Node 22/24/26 Linux + Node 24 Windows, tag-triggered npm trusted publishing (OIDC, actions pinned to SHAs).Before tagging
gulp-svgoon npmjs.com (this repo,publish.yml) — the publish workflow has no token secret.Testing
15/15 tests, strict typecheck, lint, and build pass locally; CJS/ESM interop verified against
dist/. Reviewed by two GPT-5.6 Sol codex passes (implementation + test harness); all findings addressed.