Response.getHeader may be undefined, not a function

[sjy]

• Operating System: OSX
• Node Version: 10.15.1
• NPM Version: 6.4.1
• webpack version: 4.1.6
• webpack-dev-middleware Version: 3.6.1

• This is a bug

Expected Behavior

No error

Actual Behavior

A TypeError throwed

 if (!res.getHeader('Content-Type')) {
...
}

For Bugs; How can we reproduce the behavior?

Use vue-cli create a app and install the latest version of webpack-dev-middleware

[sjy]

#377 introduce this issue

[sjy]

@evilebottnawi should i need to make a pr which will check getHeader before call it

[alexander-akait]

@sjy yep, feel free to send a PR, anyway what is use case where getHeader is undefined?

[sjy]

My project depends on koa-webpack, shellscape/koa-webpack#109

[alexander-akait]

@sjy we don't support officially koa, we can add check, but in future it can get other broken part

[dmohns]

Looks like help is on the way: shellscape/koa-webpack#110

[nuintun]

Same problem !!

[wssgcg1213]

same problem.

[alexander-akait]

All comments are not in English are marked as spam.

[alexander-akait]

Update your deps

[white87332]

same problem!!

[alexander-akait]

Update your deps

[emilsedgh]

Which dependency must be updated to resolve this?

It seems that koa-webpack is the package which included the fix but I'm not even using that.

Do I have to?

[jqueryisamonad]

@emilsedgh are you sure about that? Is the grep koa-webpack package-lock.json output empty?

[emilsedgh]

Yes I'm quite sure of that.

It seems that koa-webpack wrapped webpack-dev-middleware and webpack-hot-client, which were already set up.

I'm in the process of porting to koa-webpack anyways, but I think this bugs means people wont be able to opt-out of that anymore.