webpack-dev-server fails on client-side require

[pastelsky]

webpack-dev-server fails on client-side require

[pastelsky]

Yeah, hard to get it right the first time when you're typing on mobile in a metro train, using Github's dektop UI.

[pastelsky]

So here is how bundlephobia works. We emulate creation of a new project by the end user, and to the project's entry point, we import the requested package as a import pack from <requested-package>
Then, to make sure that tree shaking doesn't come into play, we "use" the imported package.

Next the project is built out using webpack, with the generated entry point, just like a user would. Now while webpack resolves packages using its resolution mechanism, it can encounter packages that it cannot find. Hence this error.

I've been trying to write a webpack resolve plugin that ignores such "missing" dependencies and moves the build forward with appropriate warning anyway, though abandoned it midway due to lack of documentation around it. Would love to accept a PR arround this.

[shellscape]

@pastelsky looks like your comment was cut off.