Host our own PDF viewer instead of using Mozilla demo page

[marcaaron]

cc @thienlnam

Fixed Issues

Fixes https://github.com/Expensify/Expensify/issues/146082

Tests

1. Verify PDFs can be viewed on web, desktop, mobile-web and there are no regressions

Screenshots

❌

[botify]

Hey, I noticed you changed some webpack configuration files. This can break production builds. Did you remember to run a production build locally to verify they still work?

[marcaaron]

• Looked into getting an iframe to work, but hit a bunch of CORB and frame ancestor errors that I couldn't easily resolve. There's probably a way to resolve them, but I'd rather look into it another day and just get this working for now as I'm not sure if the iframe will even be suitable once resolving those errors.

• Hosting these files should work fine. However, I did need to modify a file to whitelist some hosts here. This issue is explained in more detail here -> Allow foriegn origin URLs only for hosted viewers. mozilla/pdf.js#6916

• Some solutions that I think would be better, but don't feel we need to look into right now:

  • Figure out an iframe solution
  • Use pdf.js via react-pdf or a custom implementation

[botify]

Hey, I noticed you changed some webpack configuration files. This can break production builds. Did you remember to run a production build locally to verify they still work?

[botify]

Hey, I noticed you changed some webpack configuration files. This can break production builds. Did you remember to run a production build locally to verify they still work?

[TomatoToaster]

Haha, a lot simpler than the diff would suggest. The actual code changes LGTM.

Only NAB I had was wondering if all these pdf properties files could be gitingored and generated on build or something since there are so many. But if that seems overly complicated feel free to merge!

[marcaaron]

Only NAB I had was wondering if all these pdf properties files could be gitingored and generated on build or something since there are so many. But if that seems overly complicated feel free to merge!

Yeah I brought this up in engineering-chat and the consensus seems to be that it's NBD to keep things like this now and would be more effort to move it over to a separate repo and incorporate into the build process. We can always go down that road later.