Skip to content
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

Closed
Phoenixmatrix opened this issue Mar 17, 2016 · 8 comments
Closed
Assignees
Milestone

Comments

@Phoenixmatrix
Copy link

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)

@prashcr
Copy link

prashcr commented Mar 17, 2016

I'm having the same issue on OSX

@ericclemmons
Copy link
Member

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.

@samuelbirch
Copy link

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.

@prashcr
Copy link

prashcr commented Mar 18, 2016

@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.

@samuelbirch
Copy link

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

@prashcr
Copy link

prashcr commented Apr 4, 2016

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

@ericclemmons
Copy link
Member

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.

@ericclemmons ericclemmons added this to the 3.1.0 milestone Apr 15, 2016
@ericclemmons ericclemmons self-assigned this Apr 15, 2016
@ericclemmons
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants