-
Notifications
You must be signed in to change notification settings - Fork 12k
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
fix(@angular/cli): fix webdriver deep import on yarn #4597
Conversation
Doesn't seem like this fix is enough. |
How about adding |
@filipesilva As you were wondering if this was enough, your PR fixes the issue for my project (cli |
@cexbrayat I guess it doesn't work with npm anymore and that's why it is not enough? |
Yeah it doesn't work npm with this fix. Not sure what the solution is for now, but the workaround is to update webdriver manually ( |
Would it make sense to run |
That's essentially the CLI doing it the same way as the workaround. |
That's what we were trying to move away from, running npm scripts in separate processes. |
I think there are potential 2 options: 1 - Add 2 - Add a file check for one of the cases (say NPM, under I recommend just going with option 2, as this is a basic failing scenario at the moment. |
@Meligy I think something like 2 is a pretty good solution for now. Trying both and failing only if neither is there. |
d4b5931
to
e5a701a
Compare
Followup from #4597 Following @Meligy suggestion in #4597 (comment) Fix #4596
Followup from angular#4597 Following @Meligy suggestion in angular#4597 (comment) Fix angular#4596
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Fix #4596