Unable to install from forked repo as a dependency

[rushill2]

Configuration:

• Using in a web-app built with react@latest
• Ubuntu 22.4:
• PDF.js version: latest master commit

Steps to reproduce the problem:

1. Fork and use in package.json

What is the expected behavior?

1. To install on yarn install

What went wrong? (add screenshot)
Error on yarn install

user@Ubuntwo:~/frontend$ yarn cache clean
yarn install
➤ YN0000: Done in 0s 4ms
➤ YN0000: · Yarn 4.1.0
➤ YN0000: ┌ Resolution step
➤ YN0058: │ pdfjs-dist@https://github.com/_ACCOUNT_/pdf.js.git#commit=_COMMIT_: Packing the package failed (exit code 1, logs can be found here: /tmp/xfs-41fddbeb/pack.log)
➤ YN0000: └ Completed in 1m 21s
➤ YN0000: · Failed with errors in 1m 21s

pack.log is observed to be:

Packing pdfjs-dist@https://github.com/_ACCOUNT_/pdf.js.git#commit=_COMMIT_ from sources
Using npm for bootstrap. Reason: found npm's "package-lock.json" lockfile

npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated mkdirp@0.3.5: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated highlight.js@9.18.5: Support has ended for 9.x series. Upgrade to @latest
npm WARN deprecated core-js@2.6.9: core-js@<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.

> postinstall
> cross-env PUPPETEER_PRODUCT=firefox node node_modules/puppeteer/install.mjs

Firefox Nightly (nightly_127.0a1) downloaded to /home/_USER_/.cache/puppeteer/firefox/linux-nightly_127.0a1

added 1387 packages, and audited 1845 packages in 23s

188 packages are looking for funding
  run `npm fund` for details

38 vulnerabilities (15 moderate, 23 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

Do not see any errors either, just can't understand why the forked version fails. I also tried with the master branch from the forked repo to make sure the changes didn't break anything but I receive the same result. Appreciate the insight!

What I tried:

1. npm audit fix
2. yarn cache clean
3. Adding the outdated deps from the pack.log to the project package.json
4. I ran the build but did not push those files to the repo since they were part of the gitignore.

I am rather new to this, but the idea is to use the pdfFindController and other related commands but with some modifications to match my project's use case

Edit: Counterintuitively I also added the build files to the forked repo to no avail. For reference my deps in package.json resemble

"pdfjs-dist": "github:_ACCOUNT_/pdf.js.git",