Version Packages - #2904
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
September 2, 2026 13:26
0bd95d5 to
c8f2a7b
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2904 +/- ##
=======================================
Coverage 99.64% 99.64%
=======================================
Files 69 69
Lines 1961 1961
Branches 599 599
=======================================
Hits 1954 1954
Misses 7 7 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@node-minify/core@11.0.0
Major Changes
1a1be73: v11: cleanup major release.
Breaking changes
engines.nodemoved from>=20.0.0to>=22.0.0across all packages. Node 20 reached end-of-life on 2026-04-30 and is no longer covered by CI (the test matrix runs 22.x and 24.x). Upgrade to Node 22 or later.@node-minify/babel-minify,@node-minify/uglify-es,@node-minify/yui,@node-minify/sqwish,@node-minify/crass. Use the recommended replacements (terser/oxc/swc/esbuild for JS, lightningcss/cssnano for CSS).@node-minify/run: internal Java/process-spawn helper, no longer used by any compressor.@node-minify/types:CompressorReturnType(useCompressorResult) andMinifyOptions(useSettings).google-closure-compilernpm API instead of invoking the Java JAR through@node-minify/run. Same flags and output. Note: the npm package still bundlesgoogle-closure-compiler-java, so Java may still be invoked under the hood — this change removes node-minify's custom Java plumbing, not Java itself.New features
@node-minify/utils(recommended/supported/legacy/removed), surfaced in CLI help and the GitHub Action.node-minify doctor: read-only CLI command covering every v11 break. Scanspackage.json, source imports,compressor:values and workflow YAML for removed/legacy compressors, the removed@node-minify/runpackage, the removedCompressorReturnType/MinifyOptionstype aliases, andengines.noderanges that still allow Node below 22. Exits non-zero on errors so it can gate CI.bufferlimit (kills the child process when stdout/stderr exceeds it) plus hardened process/timeout/error handling.Migration
See the v11 migration guide, or run
npx --package=@node-minify/cli -- node-minify doctorin your project.Patch Changes
@node-minify/benchmark@11.0.0
Patch Changes
@node-minify/clean-css@11.0.0
Patch Changes
@node-minify/cli@11.0.0
Patch Changes
@node-minify/cssnano@11.0.0
Patch Changes
@node-minify/csso@11.0.0
Patch Changes
@node-minify/esbuild@11.0.0
Patch Changes
@node-minify/google-closure-compiler@11.0.0
Patch Changes
@node-minify/html-minifier@11.0.0
Patch Changes
@node-minify/imagemin@11.0.0
Patch Changes
@node-minify/jsonminify@11.0.0
Patch Changes
@node-minify/lightningcss@11.0.0
Patch Changes
@node-minify/minify-html@11.0.0
Patch Changes
0ec8a94: Fix
minify-htmlthrowingminifyHtmlLib.minify is not a functionat runtime.@minify-html/nodeis a CommonJS native addon, so under Node's ESM loader its exports are reachable only through the default export. The compressor calledminifyoff the namespace object, which is alwaysundefinedthere, making the package fail on every input when consumed from real Node.The bug was masked in CI: the error test mocked
@minify-html/nodewith a flat{ minify }shape that does not match the real module, and Vitest's CommonJS interop resolved the namespace differently than Node does. The mock now mirrors the real default-export shape, and a regression test asserts the interop directly.@node-minify/no-compress@11.0.0
Patch Changes
@node-minify/oxc@11.0.0
Patch Changes
@node-minify/sharp@11.0.0
Patch Changes
@node-minify/svgo@11.0.0
Patch Changes
@node-minify/swc@11.0.0
Patch Changes
@node-minify/terser@11.0.0
Patch Changes
@node-minify/uglify-js@11.0.0
Patch Changes
@node-minify/types@11.0.0
@node-minify/utils@11.0.0
@node-minify/examples@11.0.0
Patch Changes
@node-minify/action@11.0.0
Patch Changes
@node-minify/docs@11.0.0