Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update clean-css To v5.3 #150

Merged
merged 1 commit into from Apr 6, 2023
Merged

Update clean-css To v5.3 #150

merged 1 commit into from Apr 6, 2023

Conversation

korverdev
Copy link
Contributor

@korverdev korverdev commented Mar 23, 2023

Updates clean-css to the latest version. Updates a test to reflect the functionally identical but different output the latest version of clean-css produces.

Resolves #149.

@RamyaKVelivala
Copy link

When are you planning to merge this pull request, we are unable to use "html-minimizer-webpack-plugin" because of transitive dependency of "clean-css" using older version.

@DanielRuf DanielRuf merged commit 5caba1b into terser:master Apr 6, 2023
8 checks passed
@DanielRuf
Copy link
Contributor

@sibiraj-s can you handle the release of a new version? That would be great.

@RamyaKVelivala for a short-term solution please take a look at yarn resolutions and npm overrides:
https://classic.yarnpkg.com/en/docs/selective-version-resolutions/
https://docs.npmjs.com/cli/v8/configuring-npm/package-json#overrides

@korverdev korverdev deleted the update_css-clean branch April 6, 2023 18:47
@sibiraj-s
Copy link
Collaborator

Thanks @DanielRuf

Hi. These changes are now part of v7.2.0. Thanks for the contribution @Casey-Kiewit .

I’ve been having minor problems at my end hence the delay. I’ll try to keep up henceforth.

@@ -75,7 +75,7 @@
},
"dependencies": {
"camel-case": "^4.1.2",
"clean-css": "5.2.0",
"clean-css": "~5.3.2",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You really should have used ^ here so that when 5.4.x etc is out no one needs to change the package here.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can fix it in coming releases.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, if they offer to update the deps in a timely manner, sure. Otherwise, better use ^ and when tests break, someone updates the fixtures. That was the consumers won't have to wait for a new html-minifier-terser release.

Both solutions are a compromise, of course; it depends from which point of view one sees the issue. :)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I didn’t want to use ~ or ^ in case of clean-css, just pin to a fixed version. since they introduced a breaking change in semver minor. But if it a one time thing like an accident or a bug fix actually. May be we can ignore this once.

As this might allow less maintenance releases from our end, also allows users to stay upto date on security patches.

I am fine on both options have a caret or pin it. But if clean-css doesn’t follow semver or this happened more than once, I recommend pin it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, semver is hard to follow, I've been there myself 😛

Thanks for considering!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade clean-css To v5.3
5 participants