npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

cpu-arch

v1.0.4

Published

Detect CPU architecture (handles WoW64, Rosetta 2, ARM64)

Readme

cpu-arch

Detect CPU architecture (not process architecture).

Handles emulation scenarios where process.arch returns the wrong value:

  • Windows WoW64: 32-bit Node on 64-bit Windows → returns x64
  • macOS Rosetta 2: x64 Node on Apple Silicon → returns arm64
  • Windows ARM64: Any Node on ARM Windows → returns arm64

Installation

npm install cpu-arch

Usage

const cpuArch = require('cpu-arch');

console.log(cpuArch());
// => 'x64', 'arm64', 'ia32', 'arm', etc.

Why Not process.arch?

process.arch returns the architecture of the Node.js binary, not the CPU:

| Scenario | process.arch | cpuArch() | |----------|----------------|-------------| | 32-bit Node on 64-bit Windows | ia32 | x64 | | x64 Node on Apple Silicon (Rosetta) | x64 | arm64 | | Native arm64 Node on Apple Silicon | arm64 | arm64 |

This matters when selecting native binaries (e.g., @swc/core, Node.js downloads).

Return Values

| Value | Description | |-------|-------------| | x64 | 64-bit Intel/AMD | | arm64 | 64-bit ARM (Apple Silicon, ARM64 Windows/Linux) | | ia32 | 32-bit Intel/AMD | | arm | 32-bit ARM | | ia64 | Intel Itanium | | Other | Raw uname -m output (ppc64, s390x, etc.) |

Platform Detection Methods

| Platform | Method | |----------|--------| | Windows | PROCESSOR_ARCHITEW6432 / PROCESSOR_ARCHITECTURE env vars | | macOS | sysctl -in sysctl.proc_translated for Rosetta detection | | Linux | uname -m |

License

MIT