-
-
Notifications
You must be signed in to change notification settings - Fork 198
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
dev-server default port is not added any more #565
Comments
I'm not sure arguments can be passed in camel case, normally we pass See more at https://webpack.js.org/configuration/dev-server/#devserverdisablehostcheck |
Oh, I've noticed that on another project, where I yet not updated dependencies such requests are fired: |
Hi @bravik, I did a quick test and it seems to work fine with the latest version of Encore and its dependencies:
Wouldn't you happen to have something in your |
Hey @Lyrkan I have same problem. I just updated the package to version 0.27.0 and got error with sockjs. At the moment we use command like this: All assets are server with right port and works: But sockjs is served with host and port like this: Any idea why? |
@Lyrkan Also tried to locate the URL and under |
@Lyrkan nothing special. Actually I've done no changes to webpack.config.js at all. Just |
@Lyrkan okay si I reverted It's in here: webpack/webpack-dev-server#1777 |
Oh, so that only happens when you are retrieving assets from the dev-server in a page that isn't handled by it? That would explain why I didn't see the issue during my previous test :) Not much we can do on our side then (except maybe pinning the In the meantime, if you are using Yarn you can add a |
Yep, I installed specific version |
@bravik Does it also solve your issue? |
@Lyrkan I've just added specific --port and it works for now. |
if you add --port |
Seems to be an open issue on webpack-dev-server's end: webpack/webpack-dev-server#1796 |
@aarongerig Doesn't seem to be the same issue to me. As pointed by @ondrajonas it was most likely related to webpack/webpack-dev-server#1777 which should be fixed in the next version of |
Hey @Lyrkan, had the same problem when using Vue/Hot Module Reloading using version 0.27.: (CORS Access-Control-Allow-Origin) Thanks to your comments solved it with running: or easier by adding the port and disable-host-check in package.json: Thanks! |
had the same problem , |
Using |
Thank you for this issue. |
This week something did updated, and I have Cross-Origin request errors for
GET /sockjs-node/info
requests flooding the console and preventing auto-reloading on changes.I have in package.json:
"start": "encore dev-server --disableHostCheck",
and commit this file to repository, so I could easily start dev-server with
npm start
on any deployment and not specify particular host. But obviously--disableHostCheck
flag doesn't work anymore.Furthermore, when I add
--host myhost.loc
GET /sockjs-node/info
return 404 errors.
The text was updated successfully, but these errors were encountered: