You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which @angular/* package(s) are the source of the bug?
localize
Is this a regression?
Yes
Description
When I install @angular/localize in newly created angular project, jasmine types (describe, it, expect, afterAll etc) are not recognized inside *.spec.ts:
To reproduce:
ng new Angular15.net
cd Angular15.net
ng add @angular/localize
# code .
(these error messages are in czech - see below for english error messages)
Please provide a link to a minimal reproduction of the bug
ng new Angular15.net
cd Angular15.net
ng add @angular/localize
# code .
Please provide the exception or error you saw
describe():
Cannot find name 'describe'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha` and then add 'jest' or 'mocha' to the types field in your tsconfig.(2593)
it():
Cannot find name 'it'. Do you need to install type definitions for a test runner? Try `npm i --save-dev @types/jest` or `npm i --save-dev @types/mocha` and then add 'jest' or 'mocha' to the types field in your tsconfig.(2593)
expect():
Cannot find name 'expect'.(2304)
Please provide the environment you discovered this bug in (run ng version)
Activity
kondelik commentedon Dec 10, 2022
Edit: No, I did not.
When I do it like I wrote (see below), then
then
$localizeis undefined... 😩Old comment:
kondelik commentedon Dec 17, 2022
Looking at PR #48502 - workaround right now is:
main.ts; add:and remove every mention of
from
tsconfig.jsonalan-agius4 commentedon Dec 17, 2022
"@angular/localize" types should only be removed from the root
tsconfig.json.fix(localize): add triple slash type reference on `@angular/localize`…
fix(localize): add triple slash type reference on `@angular/localize`…
angular-automatic-lock-bot commentedon Feb 4, 2023
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.