feat: switch to htmlnano

[stevenjoezhang]

Check list

• Add test cases for the changes.
• Passed the CI test.

Description

Issue resolved: #84
Issue resolved: #148

I managed to complete the migration, and the configuration options were almost entirely unaffected. Users can upgrade seamlessly without any noticeable changes.

Additional information

[tomap]

Looks good

[Copilot]

Pull Request Overview

This PR migrates the package from using html-minifier to htmlnano as the HTML minification library. The change updates the minification engine while attempting to maintain compatibility with existing configuration options.

• Replaced html-minifier with htmlnano and its dependencies (cssnano, postcss, svgo, terser)
• Updated configuration options to match htmlnano's API (e.g., minifyJS → minifyJs, minifyCSS → minifyCss)
• Converted the filter function to async and updated all tests accordingly

Reviewed Changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
package.json	Updated dependencies from html-minifier to htmlnano and added required peer dependencies
lib/filter.js	Migrated from html-minifier to htmlnano, converted function to async, added custom comment filtering logic
index.js	Updated default configuration options to match htmlnano's API
test/index.js	Updated all tests to handle async filter function and adjusted expectations for htmlnano behavior
README.md	Updated documentation to reflect new configuration options and removed trailing whitespace
.gitignore	Added package-lock.json to ignore list

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Mutating the config options object is dangerous. Since options is a reference to this.config.html_minifier, these deletions will permanently modify the configuration for subsequent calls. This will cause issues if the filter is invoked multiple times. Create a shallow copy of options before mutation: const options = { ...this.config.html_minifier };

[yoshinorin]

We have to fix this link.

[yoshinorin]

The implementation appears to be slower compared to the current one. I tested with the following configuration (there should be no difference between the two):

# Current
html_minifier:  
  collapseBooleanAttributes: true
  collapseWhitespace: true
  ignoreCustomComments: [ !!js/regexp /^\s*more/]
  removeComments: true
  removeEmptyAttributes: true
  removeScriptTypeAttributes: true
  removeStyleLinkTypeAttributes: true
  minifyJS: true
  minifyCSS: true

# This PR
html_minifier:
  collapseBooleanAttributes: true
  collapseWhitespace: true
  ignoreCustomComments: [ !!js/regexp /^\s*more/]
  removeComments: true
  removeEmptyAttributes: true
  removeRedundantAttributes: true
  removeAttributeQuotes: true
  minifyJs: true
  minifyCss: true

I only tested with Cold Processing on Hexo 8.1.1, but when generating around 2000 articles, this PR seems to be approximately 1 to 1.5 minutes slower than the current implementation.

It's unclear whether the slowdown is caused by htmlnano itself or by something in this implementation, but this performance difference might not be acceptable for some users.

[yoshinorin]

Also here.

[yoshinorin]

IMHO:

We should provide a migration guide since the configuration has changed.

[yoshinorin]

We should provide a migration guide since the configuration has changed.