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 🙏

© 2024 – Pkg Stats / Ryan Hefner

arch

v3.0.0

Published

Better `os.arch()` for node and the browser -- detect OS architecture

Downloads

36,466,986

Readme

arch ci npm downloads javascript style guide

Better os.arch() for node and the browser -- detect OS architecture

Sauce Test Status

This module is used by WebTorrent Desktop to determine if the user is on a 32-bit vs. 64-bit operating system to offer the right app installer.

In Node.js, the os.arch() method (and process.arch property) returns a string identifying the operating system CPU architecture for which the Node.js binary was compiled.

This is not the same as the operating system CPU architecture. For example, you can run Node.js 32-bit on a 64-bit OS. In that situation, os.arch() will return a misleading 'x86' (32-bit) value, instead of 'x64' (64-bit).

Use this package to get the actual operating system CPU architecture.

BONUS: This package works in the browser too.

install

npm install arch

usage

var arch = require('arch')
console.log(arch()) // always returns 'x64' or 'x86'

In the browser, there is no spec that defines where this information lives, so we check all known locations including navigator.userAgent, navigator.platform, and navigator.cpuClass to make a best guess.

If there is no affirmative indication that the architecture is 64-bit, then 32-bit will be assumed. This makes this package perfect for determining what installer executable to offer to desktop app users. If there is ambiguity, then the user will get the 32-bit installer, which will work fine even for a user with a 64-bit OS.

For reference, x64 means 64-bit and x86 means 32-bit.

Here is some history behind these naming conventions:

  • https://en.wikipedia.org/wiki/X86
  • https://en.wikipedia.org/wiki/IA-32
  • https://en.wikipedia.org/wiki/X86-64

Node.js proposal - os.sysarch()

Note: There is a proposal to add this functionality to Node.js as os.sysarch().

license

MIT. Copyright (c) Feross Aboukhadijeh.