New Angular projects install jasmine-core ~5.7.0 but use 4.6.1
- Dominant language
- TypeScript
- Stars
- 27k
- Forks
- 11.8k
- Avg merge
- 14h 23m
- Merged PRs (30d)
- 162
Description
### Which @angular/* package(s) are the source of the bug?
Don't known / other
### Is this a regression?
Yes
### Description
The package.json file generated by `ng new` includes the dev dependency `"jasmine-core": "~5.7.0"`, but jasmine-core 4.6.1 is also installed and used to run tests in Karma.
Steps to reproduce:
1. Install @angular/cli 20.0.3.
2. Run `ng new some-name` and accept all the defaults.
3. Note the jasmine-core dependency in package.json.
4. Run `npm test` and note the Jasmine version displayed in the browser.
5. Run `npm ls jasmine-core`.
Expected: The versions from steps 3 and 4 agree, and step 5 shows that only a single version of jasmine-core is installed.
Observed: Step 3 and 4 show different major versions, and step 5 shows that two different versions of jasmine-core are installed.
The problem is that karma-jasmine declares a dependency on jasmine-core 4.x. `ng new` tries to set up the project to use jasmine-core 5.x, but it doesn't add [the necessary override](https://jasmine.github.io/pages/faq.html#001-karma).
Note: I'm not an Angular user, but I do maintain Jasmine. I've seen this version mismatch cause a couple of problems. One is that Angular users are occasionally confused about which major version of jasmine-core they're actually using. The other is that it makes jasmine-core download statistics pretty much useless for determining uptake of the latest major version, since an unknown but probably large portion of 5.x downloads are from Angular users who are actually still running 4.x.
### Please provide a link to a minimal reproduction of the bug
_No response_
### Please provide the exception or error you saw
```true
```
### Please provide the environment you discovered this bug in (run `ng version`)
```true
Angular CLI: 20.0.3
Node: 20.19.0
Package Manager: npm 10.8.2
OS: darwin arm64
Angular: 20.0.4
... common, compiler, compiler-cli, core, forms
... platform-browser, router
Package Version
------------------------------------------------------
@angular-devkit/architect 0.2000.3
@angular-devkit/core 20.0.3
@angular-devkit/schematics 20.0.3
@angular/build 20.0.3
@angular/cli 20.0.3
@schematics/angular 20.0.3
rxjs 7.8.2
typescript 5.8.3
zone.js 0.15.1
```
### Anything else?
_No response_
Contributor guide
Research direction
Reproduce the issue with Angular CLI 20.0.3 by running `ng new` and inspecting the generated package.json, then run `npm test` and `npm ls jasmine-core`. Trace the Angular CLI project-generation source that defines the Jasmine and Karma dependencies; done means the declared and runtime versions agree and npm installs only one jasmine-core version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- cli, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100