webpack-dev-server doesn't find packages right after they're installed about install-webpack-plugin HOT 8 CLOSED

I'd recommend using the 2.0.2 release.

#29 will solve both the problems in 3.x as well as keep the features missing in 2.x, but require a significant amount of diving into code that only sokra knows.

from install-webpack-plugin.

I'm having the same issue on OSX

from install-webpack-plugin.

Yep, this is an issue I was having as well. Webpack's a confusing ball of mud, so it'll get fixed (eventually). It was the sacrifice made to support resolve.root and resolve.alias.

from install-webpack-plugin.

A quick fix could be to restart webpack? - If you could give any pointers as to where in my version i can hack that would be great.

from install-webpack-plugin.

@samuelbirch Easier fix would be to just Ctrl-S any file being watched by WDS, so you don't have to startup the server again.

from install-webpack-plugin.

@prashcr I could live with that, but that doesn't work for me. I have to restart webpack in order to get it working.

from install-webpack-plugin.

@samuelbirch I'm taking a stab in the dark, but are you using WebStorm by any chance?

from install-webpack-plugin.

I think I have this mostly resolved in v3.1.0. Please track that release.

There's really no way for me to get this working 100%. Resolving loaders is great, but normal modules is abysmal.

It's as if Webpack's like "Sure, I'll let you install this dependency first, but I already checked and it wasn't there so I don't care what you think!".

Unless someone is very knowledgeable with Webpack's inner workings & can help resolve this (the /example is a fantastic testing ground), I'm on my own.

from install-webpack-plugin.