sandbox-npm-install

Use this skill whenever: 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. Run the bundled install script from the workspace root: If verification fails, run the script again — crashes can be intermittent during initial setup. After the script completes, verify your toolchain works. For example: If your project uses Vite, you may need to allow the symlinked path in server.fs.allow . Add the symlink target's parent directory (e.g., /home/agent/project-deps/ ) to your Vite config so that Vite can serve files through the symlink. - 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 - 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 - Copies package.json , package-lock.json , and .npmrc (if present) to a local ext4 directory -...