mapbox / mapbox/node-pre-gyp

building sharp fails

Open
#487 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.2k
Forks
271
Avg merge
23h 40m
Merged PRs (30d)
2

Description

Buiding the "sharp" npmjs package fails

Env:

$ node -v
v13.8.0
$ node-gyp.js -v
v6.1.0
$ node-pre-gyp -v
v0.14.0
$ env|grep NODE
NODE_PATH=/usr/lib/node_modules;/usr/lib/node_altmodules

This is the log part:

node-pre-gyp info it worked if it ends with ok
node-pre-gyp info using node-pre-gyp@0.14.0
node-pre-gyp info using node@13.8.0 | linux | x64
node-pre-gyp ERR! UNCAUGHT EXCEPTION
node-pre-gyp ERR! stack Error: sharp package.json is not node-pre-gyp ready:
node-pre-gyp ERR! stack package.json must declare these properties:
node-pre-gyp ERR! stack binary.module_name
node-pre-gyp ERR! stack binary.module_path
node-pre-gyp ERR! stack binary.host
node-pre-gyp ERR! stack at validate_config (/usr/lib/node_modules/node-pre-gyp/lib/util/versioning.js:220:15)
node-pre-gyp ERR! stack at Object.module.exports.evaluate (/usr/lib/node_modules/node-pre-gyp/lib/util/versioning.js:279:5)
node-pre-gyp ERR! stack at clean (/usr/lib/node_modules/node-pre-gyp/lib/clean.js:17:27)
node-pre-gyp ERR! stack at Object.self.commands. [as clean] (/usr/lib/node_modules/node-pre-gyp/lib/node-pre-gyp.js:52:37)
node-pre-gyp ERR! stack at run (/usr/lib/node_modules/node-pre-gyp/bin/node-pre-gyp:82:30)
node-pre-gyp ERR! stack at processTicksAndRejections (internal/process/task_queues.js:79:11)
node-pre-gyp ERR! System Linux 4.19.36-std-def-alt1
node-pre-gyp ERR! command "node" "/usr/bin/node-pre-gyp" "rebuild" "--release" "--python=/usr/bin/python3"
node-pre-gyp ERR! cwd /usr/src/RPM/BUILD/npmjs-sharp-0.24.0
node-pre-gyp ERR! node -v v13.8.0
node-pre-gyp ERR! node-pre-gyp -v v0.14.0
node-pre-gyp ERR! This is a bug in node-pre-gyp.
node-pre-gyp ERR! Try to update node-pre-gyp and file an issue if it does not help:
node-pre-gyp ERR! https://github.com/mapbox/node-pre-gyp/issues

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure with the reported Node.js, node-gyp, and node-pre-gyp versions, then inspect node-pre-gyp/lib/util/versioning.js and the sharp package.json referenced in the log. Done means the sharp rebuild completes without the package configuration validation error and the relevant behavior is covered by a regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
build-system, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.