Wojciech Maj

Hmmm, not bad workaround at all! I think that this should be more talked through at `webpack-loader`'s repository though. I'm by no means a Webpack expert so perhaps they will...

Hey @benoj, setting custom PDF.js settings without the need of hacks is now live in React-PDF 2.3.0. It's not much different: ```js import { setOptions, } from 'react-pdf'; setOptions({ workerSrc:...

The important thing to note is that entry.webpack sole purpose is to enable PDF.js worker with zero configuration from your side. If you plan to disable it, you should not...

That looks okay to me ;) That if course requires you to do more configuration because you need to copy the loader yourself. By the way, that's default entry point...

@joshbrw, @tjwebb, please refer to the [comment above](https://github.com/wojtekmaj/react-pdf/issues/97#issuecomment-345368242). You don't need to force Webpack to put files anywhere you don't want them. I believe this is exactly what you are...

@b-asaf Sometimes, specially on modern apps which have client-side routing instead of 404, a HTML page is returned, so you don't see actual HTTP 404 error code, you see 200.

Hey there @Rioos, thanks for report and sorry for delay. Would you please try react-pdf@next if you're running on React 16.3? I believe this should no longer be an issue...

Hello, any news on that? :)

In 4.0.0 we're not using old context API so this must be something else in your case...

I'm not able to reproduce this, can anyone provide reproducible CodeSandbox? Here's a starting point: https://codesandbox.io/s/react-pdf-bbgek