nan VS node-pre-gyp

TypeScript has gained popularity in recent years, and to put things into perspective, it has over 29 million weekly downloads on npm. According to the Stack Overflow 2021 developer survey, it is ranked as the third most-loved programing language, beating Python, Node.js, and JavaScript itself. To learn how to set up TypeScript with node, see this article.

After sweating blood and tears I've finally managed to set up a Node C++ addon and shove a web-platform standard MediaStream object into one of its C++ methods for good. For compatibility across different V8 and Node.js versions, I'm using Native Abstractions for Node.js (nan):

In May 2022, Dane Springmeyer, the primary maintainer of node-pre-gyp, a critical tool in the Node.js ecosystem, announced his decision to step down. This wasn't just another developer moving on; for nearly a decade he had been maintaining the project.

The problem is that it determines the the system's platform and architecture using the binary compiling package node-pre-gyp and this very savior of a Github issue details how node-pre-gyp is not handling ARM architecture detection properly and basically mixing everything up. Because it's not detecting properly, even if we build our own binding with --build-from-source when installing, it still won't work because it is compiling the wrong binding file for the wrong architecture. To make matters worse, if we don't use --build-from-source, it just simply fetches the Intel precompiled binding file. napi-v6-darwin-unknown-x64

Indeed, Snowboy uses node-pre-gyp which helps to publish and install Node.js C++ addons from binaries. So when a new Node.js version is shipped, node-pre-gyp must update its listing of the supported targets by specifying the:

Node is like 95% OK with ARM chips, so you might have a tricky dependency. Every time I had problems it was related to something depending on node-pre-gyp, there is an issue about it .