How desktop/node-detect-arm64-translation works
This small Node.js library exposes a single ARM64-translation check. A consumer imports the public entry point, which re-exports a TypeScript wrapper; on Windows the wrapper calls the native addon, which checks the current process using Windows APIs and returns a boolean. On other platforms the wrapper returns undefined. The excerpts show these runtime relationships; no broader product subsystems are evident.
Main entry points: index.ts Public entry · detect-arm64-translation.ts Platform wrapper · main.cc Native detector
Components 5
Other components
- Library consumer
- Public entry
lib/index.ts - Platform wrapper
lib/detect-arm64-translation.ts - Native detector
src/main.cc - Windows APIs
Connections 4
- Library consumer → Public entry: imports
README.md - Public entry → Platform wrapper: re-exports
lib/index.ts - Platform wrapper → Native detector: loads and calls
lib/detect-arm64-translation.ts - Native detector → Windows APIs: queries process
src/main.cc