Support for M-chip (arm64)

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
javascript
Domain
build-system

Research direction

Locate the dependency declaration for mapnik@4.4.0 and review how dependencies are installed in this repository. Update it to the ARM64-supporting Mapnik version named in the issue, then run npm install on an Apple Silicon machine and confirm installation also remains supported on Intel.

Written by the indexing model from the issue text.

Description

Hi @mapbox/spritezero maintainers, first of all thank you for this great library! I recently switched my development machine from an Intel-based MacBook to one with Apple’s M-series chip and noticed that the current dependency on mapnik@4.4.0 fails to install on Apple Silicon. The Mapnik team added native ARM64 (M-chip) support in @mapnik/mapnik@4.6.0, so updating the dependency to the lastest version would restore compatibility and ease installation for M-chip users.

Steps to reproduce the issue:
On an M-chip MacBook, clone this repo and run npm install
Observe build errors related to mapnik@4.4.0 not providing ARM64 binaries.

Expected behavior:
npm install should complete successfully on both Intel and Apple Silicon machines by using an ARM-compatible Mapnik.

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.