-
-
Notifications
You must be signed in to change notification settings - Fork 133
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.
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
Build Error TS4090 when using Protractor #1090
Comments
I could not reproduce this issue. But I encountered another typing issue with latest TypeScript even without protractor, just with default webpack typescript jest app.
|
typeRoots also solves the issue I saw. I will get the fix in. |
Can you remove your dependency on @types/q? Protractor is going to provide it anyways |
@zewa666 i tried to remove @types/q but it cannot be removed, it exists in the package-lock probably is a dependency. You must manualy remove the conflicting @types/xxx from protractor/node_modules in order the au build to work |
For reference, @MichaelPetrinolis noticed the issue can be reproduced with
The conflicting @types/q is from cssnano (by selecting postcss-typical).
|
I downloaded aurelia cli fresh today, created a project with typescript using protractor. Got the same message. Update: Also tried adding the |
Aurelia Cli is still in beta 15 so the fix for protractor with cssnano is not included. What options do you use to create the new project? What error do you get? |
the commit attached this issue adding the The change to |
I'm submitting a bug report
Library Version:
1.0.0-beta.15
Operating System:
Windows [10]
Node Version:
v10.15.0
NPM Version:
6.4.1
Browser:
Chrome 73
Language:
TypeScript 3.4
Loader/bundler:
Webpack
Current behavior:
au run returns
[tsl] ERROR
TS4090: Conflicting definitions for 'q' found at 'xxx/node_modules/@types/q/index.d.ts' and 'xxx/node_modules/protractor/node_modules/@types/q/index.d.ts'. Consider installing a specific version of this library to resolve the conflict.
What is the expected behavior?
should compile
What is the motivation / use case for changing the behavior?
the OOB experience should be succesful
if define typesRoots in tsconfig.json the problem is solved
The text was updated successfully, but these errors were encountered: