Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

impossible to install because source code can't be gotten from amazon cloud

Open
#82 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reproducing installation with the Node 13, 12, and 10 versions mentioned, then inspect the node-pre-gyp download failure for mapnik@3.7.2 and the build/Release output from node-mapnik. Done means spritezero can be installed successfully without the reported Amazon Cloud download failure.

Written by the indexing model from the issue text.

Description

estimate-2 groomed jira-sync-complete p3

Because source code can't be gotten from amazon cloud, it's impossible to install. And also it's same when I tried with node@12 or node@10.

node-pre-gyp ERR! Tried to download(403): https://mapbox-node-binary.s3.amazonaws.com/mapnik/v3.7.2/node-v79-darwin-x64-Release.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for mapnik@3.7.2 and node@13.6.0 (node-v79 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp ERR! Tried to download(undefined): https://mapbox-node-binary.s3.amazonaws.com/mapnik/v3.7.2/node-v79-darwin-x64-Release.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for mapnik@3.7.2 and node@13.6.0 (node-v79 ABI, unknown) (falling back to source compile with node-gyp)

[Update]
I tried direct source build from node-mapnik to make my own pre-built like below:

git clone https://github.com/mapnik/node-mapnik
make

Finally I got the pre-built, mapnik.node came out in build/Release directory as a build result.
What should I do next?

Dominant language
JavaScript
Stars
186
Forks
70
PR merge metrics
No merged PRs in 30d

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.

More from mapbox/spritezero

All issues in mapbox/spritezero

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.