-
Notifications
You must be signed in to change notification settings - Fork 12k
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
Angular CLI 12 generates a project with 35 npm vulnerabilities #20795
Comments
Blocked on csstools/postcss-preset-env#191 |
Probably the best place for this, with the current postcss-present-env package @angular-devkit/build-angular is also using PostCSS v7 and v8, which has its own errors:
When running the following command:
I can see that postCSS V8 is used in: Then the following dependencies use V7: |
Seeing the same thing in Angular 11.2.14 project, but following a different path to postcss:
running
|
I have updated a project to angular 12.0.1 and when running The following dependencies use V7: |
@jimmyengman you shouldn't need resolve-url-loader now as it is a dependency of @angular-devkit/[email protected] but upgrading postcss-preset-env is something I am also looking into to see if I can help with some PR's etc to bring it inline with V8. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@angular-devkit/build-angular version 0.1102.14 |
glob-parent: #21097 css-what:
postcss: bholloway/resolve-url-loader#198 |
Closing as the original reported issue should be addressed now since postcss released a security fix in 7.0.36. More info: https://npmjs.com/advisories/1693 |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
After installing the latest CLI (v12) I decided to generate a clean new project to see what's different and what's being generated. Unfortunately I found out that the generated project has 35 severity vulnerabilities in the npm packages right off the bat. The vulnerabilities are not critical but they can't be resolved automatically using
npm audit fix
. The audit report shows all the vulnerabilities in the following way:I hope that I reported the issue in the correct repository.
The text was updated successfully, but these errors were encountered: