webpack/webpack-cli

Error: Cannot find module '@webpack-cli/serve/lib/startDevServer'

timoaudi opened this issue · 7 comments

timoaudi commented

Describe the bug

Since the release of webpack-cli 4.8.0 we get the error below.

What is the current behavior?

When running the CLI we get:

Error: Cannot find module '@webpack-cli/serve/lib/startDevServer'

Reason

When @webpack-cli/serve@1.5.2 was upgraded from 1.5.1 startDevServer.ts was deleted which is why the file is not found: https://github.com/webpack/webpack-cli/compare/@webpack-cli/serve@1.5.1...@webpack-cli/serve@1.5.2

alexander-akait commented

Thank you for creating this issue. However, issues need to follow one of our templates so that we can clearly understand your particular circumstances.

Please fill out all fields, I can't help you, I will reopen when you do it.

Also check @webpack-cli/serve should not be installed directly

jaipresto commented

Hey @alexander-akait . You've introduced a breaking change in a fix. Is it documented somewhere that @webpack-cli/serve should not be installed directly?

alexander-akait commented

You just have multiple @webpack-cli/serve versions in your node_modules, run npm ls @webpack-cli/serve, so you got this problem, you can install @webpack-cli/serve directly but we don't ask for this anywhere, this is an internal package,
therefore we don't ask do not install it directly

jaipresto commented

There is not multiple versions installed. We were using @webpack-cli/serve/lib/startDevServer directly.

alexander-akait commented

You should not use @webpack-cli/serve/lib/startDevServer directly, it is internal

jaipresto commented

I think what you are saying is that I should not install @webpack-cli/serve directly but I can install @webpack-cli/serve directly but I should not use @webpack-cli/serve/lib/startDevServer directly.

alexander-akait commented

We don't have public API for usage right now, so using something from @webpack-cli/serve/path/to/file.js is not safe and never was safe