-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Duplicate identifier error #3792
Comments
Yup, we'll change this. Thanks for reporting it. |
…dated dependencies closes angular#3792
- update outdated dependencies - move @types/jasmine to devDependencies closes angular#3792
- update outdated dependencies - move @types/jasmine to devDependencies closes angular#3792
Since this is a potential breaking change to existing jasmine users, I've opened PR #3795 to fix this in the upcoming release for selenium3 in the beta branch. This specific package does not require We still use A work around would be to set your types array in your tsconfig and to not include
from https://www.typescriptlang.org/docs/handbook/tsconfig-json.html |
- update outdated dependencies - move @types/jasmine to devDependencies closes #3792
closed with #3795 |
- update outdated dependencies - move @types/jasmine to devDependencies closes angular#3792
- update outdated dependencies - move @types/jasmine to devDependencies closes #3792
- update outdated dependencies - move @types/jasmine to devDependencies closes angular#3792
- update outdated dependencies - move @types/jasmine to devDependencies closes angular#3792
- update outdated dependencies - move @types/jasmine to devDependencies closes #3792
- update outdated dependencies - move @types/jasmine to devDependencies closes #3792
- update outdated dependencies - move @types/jasmine to devDependencies closes #3792
- update outdated dependencies - move @types/jasmine to devDependencies closes #3792
- update outdated dependencies - move @types/jasmine to devDependencies closes #3792
- update outdated dependencies - move @types/jasmine to devDependencies closes #3792
- update outdated dependencies - move @types/jasmine to devDependencies closes #3792
Since jest functions are global, their typing tends to conflict with other global properties in global space. This commit moves jest typings to devDependencies, where they won't be included for projects that require jest-fetch-mock. This is very similar to a protractor issue, reference here- angular/protractor#3792 angular/protractor#3795
6.9.1
4.0.11
2.1.2
chrome, ubuntu 16 LTS
Shouldn't https://github.com/angular/protractor/blob/master/package.json#L15 be declared as a dev dependency?
Opened up this bug after submitting: DefinitelyTyped/DefinitelyTyped#13064
I've started a new angular2 project and included the following dev dependency:
"@types/mocha": "2.2.33",
It installs correctly however when I run:
webpack --config webpack.config.dev.js --progress --profile --watch
I get:
My webpack config file:
Same thing happens with @types/jasmine:
Just found out that the errors:
Apparently this happens when I write my tests with mocha and use protractor for e2e tests.
The text was updated successfully, but these errors were encountered: