Search Results for "continue-binary-win-arm64.exe"

...Returns the current package's binary absolute path. When no package.json or binary can be found, undefined is returned instead.

Download a specific version of Node.js. The Node.js release is downloaded, uncompressed and untared to an executable file ready to run. node >=14.18.0 must be globally installed. However any Node version can be downloaded. This package is an ES module and must be loaded using an import or import() statement, not require(). Node.js binary's CPU architecture. This is useful for example when you're on x64 but would like to run Node.js x32.

...For creating distributables like installers and Linux packages, consider using either Electron Forge (which uses Electron Packager internally), or one of the related Electron tools, which utilizes Electron Packager-created folders as a basis. Note that packaged Electron applications can be relatively large. A zipped, minimal Electron application is approximately the same size as the zipped prebuilt binary for a given target platform, target arch, and Electron version (files named electron-v${version}-${platform}-${arch}.zip). Building an Electron app for the Windows target platform requires editing the Electron.exe file. Currently, Electron Packager uses node-rcedit to accomplish this.