You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m currently creating a Web site for myself, and I have a build script written in Python. The build script uses minify-html. Now that I’ve added CSS to my project, I want to minify it as well. Here’s the problems that I’m running into:
Using a separate Python package would be inefficient. There would be two copies of esbuild, one for minify-html and another for the other package.
Here’s why I think it makes sense to include minify_css and minify_js in the public API:
Most people probably want to use the same minifier for inline CSS/JS and CSS/JS files. If minify-html switches away from eslint, then most people would probably want to switch with it. Exposing these functions makes staying consistent easy.
In some cases (like with Python packages), it results in one less copy of eslint.
The functions need to exist anyway, so it (hopefully) wouldn’t be too much of a burden to maintain.
The text was updated successfully, but these errors were encountered:
I’m currently creating a Web site for myself, and I have a build script written in Python. The build script uses minify-html. Now that I’ve added CSS to my project, I want to minify it as well. Here’s the problems that I’m running into:
Here’s why I think it makes sense to include
minify_css
andminify_js
in the public API:The text was updated successfully, but these errors were encountered: