-
-
Notifications
You must be signed in to change notification settings - Fork 59
Problem different build and prod environments
Eugene Lazutkin edited this page Mar 24, 2026
·
1 revision
node-gyp compiles for the current platform. Copying the result to a different environment can cause ABI mismatches or other problems — for example, different CPU instruction sets between build and production machines.
The most common case is Docker: an image built on a developer's Mac may run on a Linux VM in AWS with a different CPU.
Make sure your build and execution environments match. Ideally, run npm ci inside the target environment (e.g., during Docker image execution, not during image build).
Relevant links:
- #91 — example of this problem.
- install-artifact-from-github — controlling precompiled artifact downloads.
Installing
Troubleshooting
- Problem: ABI mismatch in Electron
- Problem: build vs prod environments
- Problem: non-ASCII install path
Developers
Research and notes
- Notes on building alternatives
- Related projects
- FilteredRE2 evaluation
- RE2 lookbehinds fork assessment
- V8 Fast API assessment
- V8 non-backtracking RegExp engine
Project
Repository · README · prebuilds via install-artifact-from-github