ENOENT: no such file or directory - util.js about pdf2json HOT 10 CLOSED

@FHoxhaDev Full fix is on this branch, try it out and let me know if it works for you:

"pdf2json": "github:kylerob/pdf2json#fix-createScratchCanvas-import"

It looked good in my tests.

from pdf2json.

@kylerob by pointing my "pdf2json" in package.json will it point to your branch?

EDIT: it does resolve that issue. Thanks Kyle!

from pdf2json.

thanks to @kylerob. A more thorough fix plus appropriate tests are in PR #338, please review and test it out

from pdf2json.

Hi @modesty,

Is this an issue with Vercel or with the package itself? Is there any workaround to fix this error?

from pdf2json.

It's an issue with Vercel and executing this code on the server side due to edge functions. The issue is all of these files, the first of which you're seeing an error for, can't be read on the edge function because it hasn't been copied over by Vercel's edge function setup code. Vercel usually does a good job including what you need, but that's if you're importing code via module imports. This code is building up a string of all those file contents and eval'ing it.

I have a fork with a semi-working version that creates the big import file in a separate step, and then imports it into the main files so Vercel includes everything. I'm working on fixing an issue with a canvas function that's defined in one file and used in another that's not working, but you can try it out if you want. If I get it working today I'll create a PR in the main repo to get it merged into the baseline.

from pdf2json.

Hi @kylerob ,

Thank you for your fix. Unfortunately, for me it didn't work. It is failing at my API call where it uploads the file, this is my endpoint:

https://gist.github.com/FHoxhaDev/59e2dc2b1cc134b6d064b96573a51145

and this is the error:

Locally it works but not on Vercel host.

from pdf2json.

@FHoxhaDev Try forcing a redeploy on Vercel -- I ran into the same issue at first. Vercel seems to cache npm packages, because I've had trouble getting it to bring in my latest npm changes sometimes.

from pdf2json.

Hey @kylerob, thanks for your fix!

I just wanted to ask some quick questions.

1. Any plans on making a PR with this fix at any point?
2. If not, any plan to publish a separate npm package with your fork

I ask so we can install by doing a normal "pdf2json": "x.x.x" or even a "vercel-pdf2json": "x.x.x" instead of the current github thing

Cheers!

from pdf2json.

@modesty Thanks for bringing it home!

from pdf2json.

fixed in 3.1.2

from pdf2json.