Skip to content
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

Closed
Michel73 opened this issue Feb 7, 2019 · 2 comments · Fixed by #13614
Closed

--base-url has no effect #13611

Michel73 opened this issue Feb 7, 2019 · 2 comments · Fixed by #13614

Comments

@Michel73
Copy link

Michel73 commented Feb 7, 2019

🐞 Bug report

The option --base-url has no effect.

Command (mark with an x)

- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [x] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Is this a regression?

Yes, the previous version in which this bug was not present was: 6.x.x

Description

The option --base-url has no effect on the e2e-command. Also the baseUrl-entry in the protractor.conf.js has no effect.

🔬 Minimal Reproduction

Create new project via ng new demo and there modify the e2e-script or the protractor.conf.js as described. It has no affect. The app is always started at http://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




macos
@angular/cli@7.3.0 

Anything else relevant?

@alan-agius4 alan-agius4 added type: bug/fix freq1: low Only reported by a handful of users who observe it rarely severity5: regression area: devkit/build-angular labels Feb 7, 2019
@ngbot ngbot bot added this to the Backlog milestone Feb 7, 2019
@alan-agius4 alan-agius4 removed freq1: low Only reported by a handful of users who observe it rarely severity5: regression type: bug/fix labels Feb 7, 2019
@ngbot ngbot bot modified the milestones: Backlog, needsTriage Feb 7, 2019
@alan-agius4
Copy link
Collaborator

alan-agius4 commented Feb 7, 2019

@Michel73, most likely the root cause of this is that you have a devServerTarget specified. Hence it will always use the this.

Can you try

ng e2e --dev-server-target="" --base-url <url here>

I think we should emit an error when both base-url and dev-server-target are specified.

alexeagle pushed a commit that referenced this issue Feb 9, 2019
…vServerTarget` are used in protractor

Users cannot use both baseUrl and devServerTarget, and the later superseeds the baseUrl.

Fixes #13611
alexeagle pushed a commit that referenced this issue Feb 9, 2019
…vServerTarget` are used in protractor

Users cannot use both baseUrl and devServerTarget, and the later superseeds the baseUrl.

Fixes #13611
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants