Cannot find type definition file for 'jasmine'
See original GitHub issueIs this a regression?
No
Description
We just upgraded
from Angular 11 + Jest 26 + Spectator 7
to Angular 12 + Jest 27 + Spectator 8
and after managing to put all the dependencies in place, we’re getting this:
I’ve tried to install @types/jasmine but it conflicts with @types/jest
is it possible to move that “workaround” to somewhere else in the package config?
Thanks in advance
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in
No response
Anything else?
No response
Do you want to create a pull request?
No
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Using Jest I get: Cannot find type definition file for 'jasmine'
Go to tsconfig.spec.json in the types field under the compilerOptions and remove jasmine and add jest
Read more >Cannot find type definition file for 'jasmine/v2' #94 - GitHub
After update to newest version (@types/jasmine 3.4.1 and @types/jasminewd2 2.0.7). I'm still missing the v2 folder with the definition.
Read more >Cannot find type definition file for 'node' in TypeScript
To solve the error "Cannot find type definition file for node", install the node types by running npm i -D @types/node . If...
Read more >@types/jasmine - npm
TypeScript definitions for Jasmine. Latest version: 4.3.1, ... Start using @types/jasmine in your project by running `npm i @types/jasmine`.
Read more >cannot find type definition file for 'jasmine
Answer 1. Looks like the typings in cordova-plugin-file-transfer is incorrect. It should be an external module but it is currently a script file...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@NetanelBasal should I reopen and rename the issue to have
createKeyboardEventforjest?@bboyle so far I’ve been able to avoid this error importing from
@ngneat/spectator/jestin my spec files. The only import I need from@ngneat/spectatoris todefineGlobalsInjectionsin the jest setup file.