-
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
--base-url has no effect #13611
Comments
@Michel73, most likely the root cause of this is that you have a Can you try
I think we should emit an error when both |
…vServerTarget` are used in protractor Users cannot use both baseUrl and devServerTarget, and the later superseeds the baseUrl. Fixes #13611
…vServerTarget` are used in protractor Users cannot use both baseUrl and devServerTarget, and the later superseeds the baseUrl. Fixes #13611
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. |
🐞 Bug report
The option
--base-url
has no effect.Command (mark with an
x
)Is this a regression?
Yes, the previous version in which this bug was not present was: 6.x.xDescription
The option
--base-url
has no effect on thee2e
-command. Also thebaseUrl
-entry in theprotractor.conf.js
has no effect.🔬 Minimal Reproduction
Create new project via
ng new demo
and there modify thee2e
-script or theprotractor.conf.js
as described. It has no affect. The app is always started athttp://localhost:4200
and the browser also opens this url.I have to run the tests in a no-serve scenario on a different url.
🔥 Exception or Error
🌍 Your Environment
Anything else relevant?
The text was updated successfully, but these errors were encountered: