8000 @angular-devkit/build-angular@19.2.11 not published, causing install errors with @angular/cli@19.2.11 · Issue #30317 · angular/angular-cli · GitHub
[go: up one dir, main page]
Skip to content

@angular-devkit/build-angular@19.2.11 not published, causing install errors with @angular/cli@19.2.11 #30317

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.

Sign up for GitHub

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

Jump to bottom
Closed
1 task
LakshminadhSDx opened this issue May 15, 2025 · 5 comments
Closed
1 task

@angular-devkit/build-angular@19.2.11 not published, causing install errors with @angular/cli@19.2.11 #30317

LakshminadhSDx opened this issue May 15, 2025 · 5 comments

Comments

@LakshminadhSDx
Copy link

Command

new

Is this a regression?

  • Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

When I run ng new my-app, the process fails with the error:
No matching version found for @angular-devkit/build-angular@^19.2.11.
I expected the Angular CLI to create a new project successfully.

Minimal Reproduction

Open terminal
Run ng new my-app
Wait for dependencies to install
See the error

Exception or Error

npm ERR! code ETARGET
npm ERR! notarget No matching version found for @angular-devkit/build-angular@^19.2.11.

Your Environment

Angular CLI: 19.2.11
Node: 22.15.1
Package Manager: npm 11.0.0
OS: win32 x64

Anything else relevant?

I have not modified any configuration files.
This happens with a fresh install of Angular CLI.

Image
@JeanMeche
Copy link
Member

There is probably an issue with your registry.
The version is available as seen here : https://www.npmjs.com/package/@angular-devkit/build-angular/v/19.2.11

@JeanMeche JeanMeche closed this as not planned Won't fix, can't repro, duplicate, stale May 15, 2025
@LakshminadhSDx
Copy link
Author

Thanks @JeanMeche for quick reply

before posting here, I cross checked available versions using command "npm view @angular-devkit/build-angular versions "

FYI, please check below attachment

Image

@JeanMeche
Copy link
Member

That confirms it, a lot of versions are missing in that list.

@jkrems
Copy link
Contributor
jkrems commented May 15, 2025

FWIW, the following will print which URL the CLI is hitting to look for versions:

npm --verbose view @angular-devkit/build-angular versions

E.g. it should print a line like this if it uses upstream npm for metadata:

npm http fetch GET 200 https://registry.npmjs.org/@angular-devkit%2fbuild-angular 137ms (cache revalidated)

@LakshminadhSDx
Copy link
Author

Thanks @jkrems

when I executed the command "npm --verbose view @angular-devkit/build-angular versions" it's pointing to our organization registry. It's missing in that registry bcoz that this error is coming. Sorry I didn't know about this.

The issue is resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jkrems @JeanMeche @LakshminadhSDx
0