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

windows-binary-architecture

v1.1.2

Published

Find the architecture EXE and DLL files are built for.

Downloads

403

Readme

windows-binary-architecture

Installation

# with npm
npm install windows-binary-architecture

# with yarn
yarn add windows-binary-architecture

What is this about

Find the target CPU architecture of Windows binaries (DLLs, EXEs and others).

The module exposes a single function, getTargetArch(path, callback(err, archName, archCode)) which opens an executable file and determines what CPU architecture the file was built for, by calling your callback with a name for the architecture and its code, according to the table on the Windows documentation, reproduced here.

|Name|Value|Description| |--|--|--| |UNKNOWN| 0x0| The contents of this field are assumed to be applicable to any machine type| |AM33| 0x1d3| Matsushita AM33| |AMD64| 0x8664| x64| |ARM| 0x1c0| ARM little endian| |ARM64| 0xaa64| ARM64 little endian| |ARMNT| 0x1c4| ARM Thumb-2 little endian| |EBC| 0xebc| EFI byte code| |I386| 0x14c| Intel 386 or later processors and compatible processors| |IA64| 0x200| Intel Itanium processor family| |M32R| 0x9041| Mitsubishi M32R little endian| |MIPS16| 0x266| MIPS16| |MIPSFPU| 0x366| MIPS with FPU| |MIPSFPU16| 0x466| MIPS16 with FPU| |POWERPC| 0x1f0| Power PC little endian| |POWERPCFP| 0x1f1| Power PC with floating point support| |R4000| 0x166| MIPS little endian| |RISCV32| 0x5032| RISC-V 32-bit address space| |RISCV64| 0x5064| RISC-V 64-bit address space| |RISCV128| 0x5128| RISC-V 128-bit address space| |SH3| 0x1a2| Hitachi SH3| |SH3DSP| 0x1a3| Hitachi SH3 DSP| |SH4| 0x1a6| Hitachi SH4| |SH5| 0x1a8| Hitachi SH5| |THUMB| 0x1c2| Thumb| |WCEMIPSV2| 0x169| MIPS little-endian WCE v2 | |null| — | Unknown architecture, name is null and the architecture code is sent to the callback as-is|