Damian Kaczmarek
Damian Kaczmarek
I confirm that it's broken.
I also just discovered this issue. Very annoying. Is there any hope?
Would be glad to see this as well.
Correct - I understand it's a minor issue. Reporting it nonetheless.
It needs to run on the same port so it needs to reuse the http server. A viable solution would be to allow hooking before the "wait for changes" middleware...
I also have a fairly complex Frontend and Backend webpack build and it's the https://github.com/dividab/tsconfig-paths-webpack-plugin/pull/85 in version 3.5.2 which makes it compile. Once we know more details I can comment...
Copying my comment from #3414 Let's add solid error handling to Fish. - Ability to detect failed non-zero exit commands and treat them as error in systematic way. - Manual...
Locking dependencies on `package.json` is no solution as it locks only direct dependencies, all indirect ones will happily install at whatever latest version matches their requirements, it's a recipe for...
> The vast majority of dependency-related app breakage happens from floating top-level dependencies (the default ^ and ~). Bumps in nested dependencies are a much rarer source of problems. Maybe...
Indeed, no compatibility needed.