`@vercel/nft` does not pick up platform-specific binaries for `sentry`
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 185
- PR merge metrics
- No merged PRs in 30d
Description
I am creating this issue as #371 was closed without the entire issue being addressed, this issue is still occurring with sentry and the sentry team was forced to implement a solution to address this issue manually.
This will no doubt occur with other packages and solutions and anyone using the previous version of sentry.
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
The report concerns @vercel/nft failing to trace platform-specific binaries used by sentry, but it names no files, tests, or reproduction steps. Start by reviewing the handling of sentry's platform-specific binaries and compare the current behavior with the workaround described by the sentry team. Done means those binaries are picked up without the package-specific manual solution, including for other affected packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100