Packaging environment
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 331
- Avg merge
- 19h 52m
- Merged PRs (30d)
- 9
Description
Sorry to bother you"
When I install @nuxt/image locally, it generates both ipx and sharp. However, I noticed that within sharp, it generates the sharp-darwin-arm64v8.node package based on the environment, but my deployment environment is Linux. Therefore, when I package it, it attempts to look for the linux-x64 package. I'm not sure how to ensure that it packages according to the target deployment environment.
Contributor guide
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 local @nuxt/image installation and inspect which sharp native package is generated for the local environment. Compare that result with the Linux deployment packaging path; done means the packaged application includes and loads the correct Linux sharp binary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, nuxt, typescript
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100