node-pre-gyp VS opn

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 .

It will use your default browser. If you want to change this behavior edit server.js in line 2315 according to your preferences. Reference: https://www.npmjs.com/package/open

I can open a new browser tab using the tool open as below:

Using this package: https://www.npmjs.com/package/open

open, to open links in the browser from the cli.

prompt open colors

Nodejs doesn't have the capabilities of the browser, so there are no windows to "open". You'll need something like https://github.com/sindresorhus/open or similar.