Skip to content

Migrate webpack-dev-server CLI to webpack-cli serve #900

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

Closed
knagaitsev opened this issue May 28, 2019 · 3 comments
Closed

Migrate webpack-dev-server CLI to webpack-cli serve #900

knagaitsev opened this issue May 28, 2019 · 3 comments

Comments

@knagaitsev
Copy link
Contributor

knagaitsev commented May 28, 2019

Is your feature request related to a problem? Please describe.
The Dev Server's CLI should live in webpack-cli. This will make project configuration easier for users, and will force minimization of configuration changes that the CLI makes, creating uniformity between the Dev Server's CLI and API.

Describe the solution you'd like

  • webpack-cli serve should call the Dev Server API, not the CLI
  • Move logic from bin/webpack-dev-server to serve package
  • Minimalize any configuration changes that the CLI makes - it should simply normalize the CLI arguments into Dev Server options, then pass it into the API, and do no further config.
  • Dev Server CLI should tell the user to switch to webpack-cli serve
  • CLI should eventually be removed from the Dev Server in a major version

Describe alternatives you've considered
N/A

Additional context

EDIT:

  • Also, tests need to be added here for webpack-cli serve
@evenstensberg evenstensberg changed the title GSoC Refactor: Migrate webpack-dev-server CLI to webpack-cli serve [ENHANCEMENT]: GSoC Refactor: Migrate webpack-dev-server CLI to webpack-cli serve Oct 31, 2019
@ematipico ematipico changed the title [ENHANCEMENT]: GSoC Refactor: Migrate webpack-dev-server CLI to webpack-cli serve Migrate webpack-dev-server CLI to webpack-cli serve Mar 11, 2020
@webpack-bot
Copy link

This issue had no activity for at least half a year.

It's subject to automatic issue closing if there is no activity in the next 15 days.

@alexander-akait
Copy link
Member

Bump

@alexander-akait
Copy link
Member

Fixed, but with a lot of bugs 😞

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants