lukeed / lukeed/webpack-messages

[Question] Does this work with webpack-dev-server?

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
247
Forks
20
PR merge metrics
No merged PRs in 30d

Description

Hi! Does this package work with `webpack-dev-server`? And if so, is there any kind of special configuration which I would need to make it work?

It doesn't seem to be working for me. Here's an overview of the relevant parts of my `webpack.config.js`:

```js
const WebpackMessages = require('webpack-messages');

const config = {
mode: 'development',
devServer: {
hot: true,
port: 3001,
historyApiFallback: true,
host: '0.0.0.0',
disableHostCheck: true,
contentBase: path.resolve(__dirname, '../dist')
},
plugins: [
new WebpackMessages({
name: 'myapp'
}),
]
};
```

Seems like it should be working, but I just get the usual (ugly) webpack output.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the webpack.config.js excerpt, especially the devServer and WebpackMessages plugin configuration, and reproduce the behavior with webpack-dev-server. Compare its output with the package's expected formatting and determine whether compatibility or special configuration is missing. Done means establishing the supported setup or documenting the limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
build-system, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.