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 have a use case in which I'm minifying multiple CSS/JS files (i.e. a call to Minify::add() or Minify::addFile() for each file followed by a call to Minify::minify()), but the minified output contains the repeated standard header comments, including those containing @license. For what it's worth, this is all our code, so it's our license.
As I've looked through the documentation and source, I haven't determined a way of removing the standard header comments (with @license) or removing them AND then adding back one standard header comment (with @license) at the top of the final minified output/file.
If this is possible and I'm simply overlooking it, any direction or tips would be appreciated. It seems it would be possible if the comment removal behavior was configurable to some extent (e.g. allowing all comments to be removed regardless of @license).
The text was updated successfully, but these errors were encountered:
I have a use case in which I'm minifying multiple CSS/JS files (i.e. a call to
Minify::add()
orMinify::addFile()
for each file followed by a call toMinify::minify()
), but the minified output contains the repeated standard header comments, including those containing@license
. For what it's worth, this is all our code, so it's our license.As I've looked through the documentation and source, I haven't determined a way of removing the standard header comments (with
@license
) or removing them AND then adding back one standard header comment (with@license
) at the top of the final minified output/file.If this is possible and I'm simply overlooking it, any direction or tips would be appreciated. It seems it would be possible if the comment removal behavior was configurable to some extent (e.g. allowing all comments to be removed regardless of
@license
).The text was updated successfully, but these errors were encountered: