Skip to content

Try and replace custom dev-server with webpack-dev-server #964

@LinusBorg

Description

@LinusBorg

Originally, back in the day, we came up with our own dev-server implementation because webpack-dev-server because at that time, it was lacking some features, like the error-overlay.

Since then, it hs improved significantly, and I'm not aware of any particular noteworthy advantage of your custom devserver over webpack's.

So I'll look into this a bit more, and if there really is no advantage left, I will work out a PR to switch the template to webpack-dev-server.

This will remove the maintainance burden for the dev server from this template and also makes it more approachable for people already familiar with webpack-dev-server.

TODO

  • Check feature parity (sucess!)
  • change webpack config and package.json scripts to use webpack-dev-server
  • Test this setup.
  • remove dead code.
  • review and close PRs / notify contributors of those PRs that may still target the now removed dev-server code.
  • Review & test

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions