Blog | loke.dev

Are your JavaScript builds mysteriously failing on different operating systems? Is your CI/CD pipeline breaking while everything works fine locally? You might be experiencing the notorious npm platform-specific dependencies bug that has been frustrating development teams for many years.

In this comprehensive guide, I'll explain exactly what this bug is, how it affects your projects, and provide step-by-step solutions to fix it once and for all.

What is the npm Platform-Specific Dependencies Bug?

The issue, tracked as npm/cli#4828, involves how npm handles platform-specific optional dependencies when regenerating the package-lock.json file. This bug specifically impacts JavaScript projects with dependencies that have native modules for different operating systems and architectures.

Here's the exact sequence that triggers the bug:

When you install a package with platform-specific optional dependencies (like @swc/core, sharp, or node-sass) from scratch, npm correctly includes all possible platform variants in the package-lock.json file.
However, if you already have node_modules installed and regenerate the package-lock.json file (by deleting it and running npm install), npm only includes the platform-specific dependency for your current machine's architecture and operating system.
When this incomplete package-lock.json is committed to version control and pulled by teammates on different architectures, npm fails to detect that their platform's dependencies are missing and silently skips installing them.

The result? Cryptic runtime errors that only appear on certain platforms, making debugging extremely difficult.

Why This Bug Impacts Your Development Workflow

This bug is particularly problematic for modern JavaScript development teams because:

Cross-platform development is increasingly common: With developers using different architectures (x64 vs ARM64/M1 Macs) on the same project
CI/CD pipelines often run on different platforms than development machines
Modern JavaScript toolchains rely heavily on native modules like @swc/core, sharp, or node-sass
The errors are silent and difficult to diagnose: npm doesn't warn you when platform-specific dependencies are missing

The issue can cause builds to fail in CI while working fine locally, or vice versa, leading to confusion, wasted debugging time, and delayed deployments.

Real-World Example: How This Bug Breaks Your Builds

Let's look at a concrete example to understand the impact:

Imagine your team has both Intel and M1 Mac users. An Intel Mac user installs dependencies and commits the package-lock.json file. When an M1 Mac user pulls the changes, the necessary ARM64 dependencies won't be installed, causing runtime errors.

For packages like @swc/core (used by many modern JavaScript toolchains including Next.js, Vite, and modern ESLint configurations), this can break linting, building, or testing processes:

// This might work on the Intel Mac but fail on M1
import { transform } from '@swc/core'
 
// The error would occur here because the platform-specific
// dependency is missing
const result = await transform(code, options)

The error message might be something cryptic like:

Error: Cannot find module '@swc/core-darwin-arm64'

How to Fix the npm Platform-Specific Dependencies Bug: Step-by-Step Solution

While a pull request has been created to fix this issue, it hasn't been merged yet. Until then, here's the most reliable workaround:

Guaranteed Fix: Regenerate package-lock.json From Scratch

Delete both node_modules and package-lock.json:
```
rm -rf node_modules package-lock.json
```
Reinstall dependencies:
```
npm install
```

This ensures that npm generates a complete package-lock.json with all platform-specific dependencies included for every architecture.

Preventing Future Issues: Best Practices for Your Team

To avoid encountering this bug repeatedly, implement these preventative measures:

Document the issue in your project's README with clear instructions on how to regenerate the lock file properly.

Add a CI check that verifies the package-lock.json contains all necessary platform-specific dependencies. Here's a simple script you could add to your CI pipeline:

# Check if package-lock.json contains all platform variants
if ! grep -q "core-darwin-arm64\|core-darwin-x64\|core-linux-x64-gnu" package-lock.json; then
  echo "Error: package-lock.json is missing platform-specific dependencies"
  exit 1
fi

Create a pre-commit hook to ensure the package-lock.json is regenerated correctly before committing:

#!/bin/sh
# Check if package-lock.json was modified
if git diff --cached --name-only | grep -q "package-lock.json"; then
  echo "Warning: Regenerating package-lock.json to include all platform dependencies"
  rm -rf node_modules package-lock.json
  npm install
  git add package-lock.json
fi

Consider alternative package managers like Yarn or pnpm that don't suffer from this specific issue.

For Package Maintainers: How to Make Your Packages More Resilient

If you maintain a JavaScript package with platform-specific dependencies, consider these improvements:

Make platform-specific dependencies non-optional if they're actually required for your package to function.

Add clear error messages when a required platform-specific dependency is missing:

try {
  // Try to load the platform-specific module
  require(`@package/core-${process.platform}-${process.arch}`)
} catch (err) {
  throw new Error(
    `Missing platform-specific dependency for ${process.platform}-${process.arch}. ` +
      `This is likely due to an npm bug. Please reinstall dependencies by running: ` +
      `rm -rf node_modules package-lock.json && npm install`
  )
}

Add a postinstall script that verifies the correct platform-specific dependencies are installed.

How to Identify If Your Project Is Affected

You might be affected by this issue if you're experiencing any of these symptoms:

Mysterious build failures on certain platforms but not others
Error messages about missing native modules
Builds that work locally but fail in CI (or vice versa)
Using packages known to have platform-specific dependencies like @swc/core, sharp, or node-sass

To check if your package-lock.json is affected, run this command to search for platform-specific dependencies:

grep 'core-darwin\|core-linux\|core-win32' package-lock.json

If you only see entries for your current platform (e.g., only core-darwin-arm64 on an M1 Mac), your lock file is likely incomplete and needs to be regenerated.

Conclusion: Ensuring Cross-Platform Compatibility in Your JavaScript Projects

The npm platform-specific dependencies bug highlights the challenges of modern JavaScript development across different environments. While we await an official fix, being aware of the issue and implementing the solutions outlined in this guide will help you maintain a smooth development workflow.

Remember these key takeaways:

Always regenerate your package-lock.json from scratch when working with platform-specific dependencies
Implement preventative measures in your development workflow
Check for symptoms of this bug when encountering mysterious build failures
Consider alternative package managers for critical projects

By following these best practices, you can avoid hours of frustrating debugging and ensure your JavaScript projects build reliably across all platforms.

Have you encountered this issue in your projects? What other npm quirks have you discovered when working across different platforms? Share your experiences in the comments below!

Did you find this article helpful? Follow me for more JavaScript development tips and solutions to common web development challenges.

Solving the npm Platform-Specific Dependencies Bug: A Complete Guide for JavaScript Developers