You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we use the proxy functionality of webpack-dev-server extensively. Not all of our proxy targets are running all the time which isn't strictly necessary for our usecase except that we stumble over the bug fixed in a233ecf, in case proxy targets are not up and running.
As we are currently locked to webpack-1 we are not able to benefit from the bugfix yet. Therefore we would be very thankful if you could release a new bugfix release 1.14.2 which incorporates a233ecf.
As an alternative we may publish a new npm release from my branch into our corporate npm repository but we would definitively would favor a official package from the public repository.
Hi @sokra,
we use the proxy functionality of webpack-dev-server extensively. Not all of our proxy targets are running all the time which isn't strictly necessary for our usecase except that we stumble over the bug fixed in a233ecf, in case proxy targets are not up and running.
As we are currently locked to webpack-1 we are not able to benefit from the bugfix yet. Therefore we would be very thankful if you could release a new bugfix release 1.14.2 which incorporates a233ecf.
I've created a webpack-dev-server-1 branch over https://github.com/Mischi/webpack-dev-server/tree/webpack-dev-server-1. Can you push that branch into your repository and publish a new npm release?
As an alternative we may publish a new npm release from my branch into our corporate npm repository but we would definitively would favor a official package from the public repository.
Yours sincerely,
Fabian
/CC @davidreher
The text was updated successfully, but these errors were encountered: