Sandbox Npm Install

If you're running npm installs inside a Docker sandbox with virtiofs mounts, you've probably hit those fun SIGILL crashes from native binaries like esbuild or rollup. This skill bundles a script that installs packages on the container's local ext4 filesystem and symlinks node_modules back into your workspace, sidestepping the mmap alignment issues that plague aarch64. You'll need to rerun it whenever package.json changes, and the symlink will look broken on your host, but that's fine since node_modules is gitignored anyway. It's a specific fix for a specific problem, and if you've been debugging segfaults in your build tools, you already know whether you need this.

skills.sh installs: 1.7K
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill sandbox-npm-install --agent claude-code

Installs into .claude/skills of the current project.

Files

Sandbox npm Install

When to Use This Skill

Use this skill whenever:

You need to install npm packages for the first time in a new sandbox session
package.json or package-lock.json has changed and you need to reinstall
You encounter native binary crashes with errors like SIGILL, SIGSEGV, mmap, or unaligned sysNoHugePageOS
The node_modules directory is missing or corrupted

Prerequisites

A Docker sandbox environment with a virtiofs-mounted workspace
Node.js and npm available in the container
A package.json file in the target workspace

Background

Docker sandbox workspaces are typically mounted via virtiofs (file sync between the host and Linux VM). Native Go and Rust binaries (esbuild, lightningcss, rollup, etc.) crash with mmap alignment failures when executed from virtiofs on aarch64. The fix is to install on the container's local ext4 filesystem and symlink back into the workspace.