-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
Customize or disable serve console message #2115
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
Comments
That's the wrong way to enable HMR. Use |
@yyx990803 if you set |
You should set |
@yyx990803 in the older EDIT: ah, just saw your response. will try, but it looks to be already requesting |
@yyx990803 Yeah, that's not going to work. Apologies if I'm not communicating thoroughly, but the devServer isn't running under my |
@chasegiunta I see. That's weird, because in this case it should just work without any configuration. If it's really not, I will need a reproduction. Or I'd suggest taking a look at https://github.com/yyx990803/laravel-vue-cli-3 |
Hmmm. That approach is going back to working from the dev server and proxying your site. I think we've had issues with this in the past, and I've seen many folks from the Laravel community & mix users who have the same dev environment as I (work in |
The title of this issue is about how to change the console message. The discussion is about something else. I understand that it was an AB problem and the discussion solves the real problem, but for people arriving here from Google there is no information about how to change the console messages from
I need a way to have the console say only:
|
I'm building an app against an API, which I mock locally, but sometimes run tests from my local setup against the public (staging) API endpoint. I can configure the endpoint URL using variables in |
What problem does this feature solve?
In non-SPA setups, the server may be operating on
localhost:8080
and serving assets from there, but the site is being viewed on a separate domainmy-php-site.test
. In order for HMR to work correctly we enabled things likeheaders: { 'Access-Control-Allow-Origin': '*' }
& set our baseUrl asThis works great, except the dev will receive this message running
serve
:What does the proposed API look like?
Potentially, if a
serveMessage
is provided, it will override any console messages.The text was updated successfully, but these errors were encountered: