The PDF text bounds are not being retrieved properly when using the Next.js sample on Vercel in the client-side.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.2k
- Forks
- 1.8k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 6
Description
We retrieve the PDF text bounds using pdfium.wasm on the client-side. However, the text bounds are not being retrieved properly when deploying Nextjs sample on Vercel in the client-side. It works properly on the Nextjs sample itself. Is there a need to change the configuration level?
Please provide a solution to resolve this issue.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the PDF text-bounds issue in the Next.js sample when deployed to Vercel, then compare it with the sample running directly. Investigate the client-side pdfium.wasm setup and any deployment configuration involved. Done means text bounds are retrieved correctly in the Vercel deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100