This repository has been archived by the owner on Jul 13, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 50
Option to set websocket path #105
Comments
@bryanlarsen do you use |
I'm using koa-webpack. |
@bryanlarsen doesn't support officially |
koa-webpack is just a thin shim over webpack-serve, so I don't mind using it directly if that helps. |
What is the correct way to use this package? With webpack-dev-server? |
@alexleung The opposite. Was created to replace WDS when it got stagnant. But then it got going again. Well webpack-serve was, and this is it's HMR package, counterpart to WDS's webpack-hot-middleware. At least i think i got all that right. I just started with this stuff yesterday and am still failing at getting HMR running for an app that has a non javascript backend (python). |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Feature Use Case
Using webpack-hot-client under some sort of orchestration system to tie together a bunch of microservers, like an ingress server in minikube or the kubernetes in docker-for-mac
Feature Proposal
Allow the websocket path to be specified both on the client and the server. I'd prefer they both be set the same so I don't need to use url-rewriting.
Current ugly workaround
setting options:
and useing the ingress:
It's an ugly hack, but by setting host.client to 'localhost/hot', the resulting url is 'ws://localhost/hot:3002'
The text was updated successfully, but these errors were encountered: