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
ng new fails with latest version of @angular/cli and npm #20719
Comments
…s in new projects Synchronizes the version pinning strategy with the other karma and jasmine project dependencies. Allows project's created with npm 7+ to successfully install. `karma-jasmine-html-reporter@1.6` requires dependency versions not present in a new 11.2.x project. Fixes angular#20719
karma-jasmine-html-reporter to patches in new projects
#20720
|
Until this is fixed, how can I create a new project? Is there a way to pass |
You can you |
Not really working, but |
|
I have an issue similar when install and create a new project |
…s in new projects Synchronizes the version pinning strategy with the other karma and jasmine project dependencies. Allows project's created with npm 7+ to successfully install. `karma-jasmine-html-reporter@1.6` requires dependency versions not present in a new 11.2.x project. Fixes #20719
|
Downgrade npm from 7 to 6 using |
|
Closed via #20720 |
|
Wait, why is @alan-agius4 closing this issue? You guys need to check if there is a workaround instead of "IGNORING" this issue. |
We didn’t ignore this, we closed it because it was solved via PR #20720 |
|
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. |
Badisi commentedMay 7, 2021
Command (mark with an
x)Is this a regression?
Yes
Description
When using the latest version of
@angular/cliandnpmthe commandng newfails during dependencies installation.(but it's working fine with
yarn)Run the following command:
The text was updated successfully, but these errors were encountered: