Skip to content

Bumping cssnano version to resolve NPMJS advisory #165

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

Closed
wants to merge 1 commit into from

Conversation

borisromanov
Copy link

I installed this libraries dependencies locally with npm install. Noticed the npm audit
was alerting of 2 high severity advisories. One of them being #1755.

After looking at the sub-dependancies in the npm audit output, I simply updated
cssnano with npm audit to see if that would resolve the advisory.

I'm attempting to patch this CVE here in order to enable an update in the rails/webpacker ruby gem.

I didn't see a CONTRIBUTING.md doc in the source, so please let me know if this meets your standards.

I installed the libraries deps locall with `npm install`. Noticed the npm audit
was alerting of 2 high severity advisories.

One of them being [NPM Advisory #1755](https://www.npmjs.com/advisories/1755).

After looking at the subdependancies in the npm audit output, I simply updated
`cssnano` to see if that would resolve the advisory.
@borisromanov
Copy link
Author

Upon further digging into the v5.0.6 release of this library, I noticed the maintainer rolled back the cssnano upgrade seen here in this diff: https://github.com/NMFR/optimize-css-assets-webpack-plugin/pull/156/files. As well as, running the tests my proposed change does seem to break some functionality.

@borisromanov borisromanov deleted the bump/cssnano-version branch June 15, 2021 02:42
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.

1 participant