-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Webpack proxy not working in Quasar V2 #9466
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
Webpack has been upgraded from v4 to v5 in I am not sure if anything is consciously changed about this, or this is a bug. But the - public: 'https://localhost:8080',
+ client: {
+ webSocketURL: 'ws://localhost:8080',
+ }, So, ideally, you would file a ticket to them, but since they removed this option that would be useless. I guess we need to wait until they release a new version with these changes and test if it's working or not, then move accordingly. So, from our side, when the Webpack team releases this change and updates their documentation, we would just need to bump the package and document this change in our docs as the For reference: |
Thanks for the speedy investigation. Some changes here that may also be of relevance to the break and already merged into the current beta: https://github.com/webpack/webpack-dev-server/pull/3185/files Makes sense to sit tight and wait for that other merged change to be released. |
There is a new version released that should hopefully fix this? https://github.com/webpack/webpack-dev-server/releases/tag/v4.0.0-rc.0 |
Gentle reminder. Are we going to bump the version for this fix? I saw 3.0.4 but with no bump. |
@yusufkandemir The update to Right now (with Old: devServer: {
sockPort: 443,
}, (This fails, because New: devServer: {
webSocketURL: {
port: 443,
},
}, (This fails, because See also: https://github.com/webpack/webpack-dev-server/blob/master/migration-v4.md |
Now a final v4.0.0 release: https://github.com/webpack/webpack-dev-server/releases/tag/v4.0.0 |
I see that Quasar webpack-dev-server has been bumped to version v4. I installed the latest version, followed the webpack-dev-server migration guide (https://github.com/webpack/webpack-dev-server/blob/master/migration-v4.md) and now the issue is resolved. Thanks. |
Thanks for the followup. |
I have just updated to the latest v2 beta:
On both versions I have the following config in my quasar.conf.js
I then start Quasar with the command
quasar dev -p 8082
.It is used because my development environment has NGINX in front of it and routes all traffic to the Quasar Dev instance through port 8081, proxying to port 8082. By having the public variable set, I have been able to allow my development environment to communicate for hot reload through this proxy.
Since the update though, it doesn't appear to be recognising the proxy. Even with the public proxy variable set, I get the error in the console:
Firefox can’t establish a connection to the server at ws://localhost:8082/ws.
The text was updated successfully, but these errors were encountered: