[Proposal] Replace html-minifier with htmlnano

[SukkaW]

html-minifier is not actively maintained anymore. Although there is a forked version html-minifier-terser, it only replaces UglifyJS with terser to support ES6 (inline <script> affected only).

There is another HTML minify tool htmlnano. I have already used it in my project (and my personal blog as well). It doesn't receive active maintenance for a while, but now I am porting html-minifier's features to htmlnano (maltsev/htmlnano#94, maltsev/htmlnano#98, and more to come).

Also, htmlnano's source code is clean and its maintainer @maltsev is currently active, which means it might receive more community contributions in the future.

[SukkaW]

cc @curbengh @jiangtj @stevenjoezhang @tomap @himself65 @yoshinorin

[tomap]

It seems interesting, do you have an example/branch where you replace html-minifier with htmlnano?

[SukkaW]

do you have an example/branch where you replace html-minifier with htmlnano?

I can bring up a draft PR as a PoC.

[maltsev]

Hey 👋

htmlnano maintainer here. It's true that I rarely contribute code to this project, but on weekends I usually have some time to review/merge PRs, answer questions, and release new versions.

Also, htmlnano is used by Parcel.

[uiolee]

• [Proposal] Replace html-minifier with htmlnano #84
• Maybe Replace html-minifier with htmlnano or html-minifier-terser due to security vulnerabilities #148

I am wish to new a package with a name like hexo-htmlnano instead of hexo-html-minifier.
How do you like?

[stevenjoezhang]

I don’t think it’s necessary to create a new plugin. For existing users of this plugin, the underlying library doesn’t really matter — as long as we ensure that the configuration options and functionality remain the same. We can simply release a new version after switching to htmlnano.

[stevenjoezhang]

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