-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
webpack-dev-server doesn't find packages right after they're installed #34
Comments
I'm having the same issue on OSX |
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 |
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. |
@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. |
@prashcr I could live with that, but that doesn't work for me. I have to restart webpack in order to get it working. |
@samuelbirch I'm taking a stab in the dark, but are you using WebStorm by any chance? |
I think I have this mostly resolved in 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 |
Not sure if it's a problem with my setup (well, it kind of has to be, since in your video it works fine, hah), but when the plugin installs a package automatically (which works very well), the webpack dev server throws an error that the package isn't there. If I ctrl+s the file again without any modification, then it works.
Kind of like if there was a race condition, and webpack tried to recompile too quickly. Any thought? This is on Windows, in case its OS specific (didn't try on OSX yet)
The text was updated successfully, but these errors were encountered: