-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
fix(cli-service): do not log absolute baseUrl in terminal, close #2877 #2900
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
module.exports = function isAbsoluteUrl (url) { | ||
// A URL is considered absolute if it begins with "<scheme>://" or "//" | ||
return /^([a-z][a-z\d\+\-\.]*:)?\/\//i.test(url) | ||
} |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Won't that break for
baseUrl: http://localhost:8081/someBasePath/
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Set baseUrl to
http://localhost:8081/someBasePath/
doesn't mean to start the dev-server onlocalhost:8081
, the dev-server would still be started on${host}:${port}
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, but doesn't the console now say " go to host: port/" even though people would have to go to "localhost:port/baseurl"?
I'm honestly confused because paths and hosts in webpack can be confusing as hell to me
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider those two cases here:
Asset files (js/css/img) are served by
webpack-dev-server
(eg. localhost:8080), and user uses a reverse proxy to access the html (eg. localhost:3000/app/). In this case,baseUrl
should be set tohttp://localhost:8080/
, but user need to openhttp://localhost:3000/app/
in browser.Asset files (js/css/img) are served by
webpack-dev-server
(eg. localhost:8080), and user uses a reverse proxy to access the asset files (eg. localhost:3000/assets/). In this case,baseUrl
should be set tohttp://localhost:3000/assets/
, and user need to go tohttp://localhsot:8080
in browser.What I want to say is, we cannot infer which url should user open in browser if user set
baseUrl
to a absolute url. What we can do is tell user "we have started your dev-server on localhost:8080"...And, yes it is confusing. 😂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome, that was very helpful. Thanks.