利用NATIVEFIER 把网站生成可执行程序

目前有非常多的在线实用工具，例如思维导图、在线转换格式等。部分在线工具还支持离线状态下使用。

如果你觉得一些经常用到的在线工具，每次都要通过浏览器访问网站后使用，比较麻烦的话，可以考虑把它生成本地应用。

目前 Chrome 浏览器就支持把网站生成桌面应用程序，不过有个弊端，那就是想要运行它，必须依赖 Chrome 浏览器。

所以今天锋哥教大家直接把网站生成 EXE 程序，无需会编程。这里要用到这个「nativefier」基于 Electron 的工具，只要通过一行代码就能生成 EXE 程序。

nativefier使用

目前「nativefier」支持多个平台，包括有 Windows、Mac、Linux，你可以在这些系统里面把网站生成可执行的程序。

1.使用「nativefier」先要安装 Node.js 程序，可以到 https://nodejs.org/zh-cn 官方网站下载，建议下载长期支持版：
https://nodejs.org/dist/v20.11.0/node-v20.11.0-x64.msi

快捷键 Win+X，运行 PowerShell(管理员)，输入下面的命令开始安装：
    npm install -g nativefier

耐心等待一会，一直到出现 Thank you for using core-js.....for polyfilling JavaScript standard library! 就是安装好了。

2.接下来就可以把网站生成程序了，运行 Node.js command prompt 输入命令：nativefier "网址"。

最后 nativefier 生成的程序默认会在 C盘，你的用户名，WIN -1 文件夹里面，运行 WIN - 1.exe 就可以了。在程序里面你可以选中文本内容，通过右键来新窗口打开、复制内容等操作。

另外官方也提供了一些参数，例如可以修改图标、修改程序的默认名称。

    nativefier --name "app名字" "网址"
    navivefier --name "app图标路径" "网址"

图标支持最大图标、最小图标，参考下面的参数：

--min-width "大小px" --max-width "大小px" --min-height "大小px" --max-height "大小px"

3.将本地网页制作成程序，在生成的命令里面添加指向的 HTML 文件，如下：

    nativefier --name "Sample" "index.html"

然后打开 \app\nativefier.json 文件，搜索 "targetURL"，把 targetURL 指定的地址修改成你的 html 路径即可。

总结

通过「nativefier」你可以简单方便的把一些在线工具打包成本地应用，还是比较不错的。

另外从官方的文档里面看到，似乎还支持嵌入 Flash 插件的支持。因为目前还有一些网站需要依赖 Flash 插件，你可以打包成单独的程序来使用。有兴趣的自己研究看看了。

相关下载

    项目地址：https://github.com/nativefier
    开源代码：https://xia1ge.lanzout.com/iZB9cova25c
    项目教程：https://github.com/nativefier/nativefier/blob/HEAD/docs/api.md 

-------------------------------------------------------------------

Node.js native addon build tool.

node-gyp - Node.js native addon build tool

node-gyp is a cross-platform command-line tool written in Node.js for compiling native addon modules for Node.js. It contains a vendored copy of the gyp-next project that was previously used by the Chromium team and extended to support the development of Node.js native addons.

Note that node-gyp is not used to build Node.js itself.

All current and LTS target versions of Node.js are supported. Depending on what version of Node.js is actually installed on your system node-gyp downloads the necessary development files or headers for the target version. List of stable Node.js versions can be found on Node.js website.

Features

• The same build commands work on any of the supported platforms
• Supports the targeting of different versions of Node.js

Installation

You can install node-gyp using npm:

npm install -g node-gyp

Depending on your operating system, you will need to install:

On Unix

• A supported version of Python
• make
• A proper C/C++ compiler toolchain, like GCC

On macOS

• A supported version of Python
• Xcode Command Line Tools which will install clang, clang++, and make.
  • Install the Xcode Command Line Tools standalone by running xcode-select --install. -- OR --
  • Alternatively, if you already have the full Xcode installed, you can install the Command Line Tools under the menu Xcode -> Open Developer Tool -> More Developer Tools....

On Windows

Install the current version of Python from the Microsoft Store.

Install tools and configuration manually:

• Install Visual C++ Build Environment: Visual Studio Build Tools (using "Visual C++ build tools" if using a version older than VS2019, otherwise use "Desktop development with C++" workload) or Visual Studio Community (using the "Desktop development with C++" workload)

If the above steps didn't work for you, please visit Microsoft's Node.js Guidelines for Windows for additional tips.

To target native ARM64 Node.js on Windows on ARM, add the components "Visual C++ compilers and libraries for ARM64" and "Visual C++ ATL for ARM64".

To use the native ARM64 C++ compiler on Windows on ARM, ensure that you have Visual Studio 2022 17.4 or later installed.

Configuring Python Dependency

node-gyp requires that you have installed a supported version of Python. If you have multiple versions of Python installed, you can identify which version node-gyp should use in one of the following ways:

1. by setting the --python command-line option, e.g.:

node-gyp <command> --python /path/to/executable/python

2. If node-gyp is called by way of npm, and you have multiple versions of Python installed, then you can set the npm_config_python environment variable to the appropriate path:

export npm_config_python=/path/to/executable/python

    Or on Windows:

py --list-paths  # To see the installed Python versions
set npm_config_python=C:\path\to\python.exe

3. If the PYTHON environment variable is set to the path of a Python executable, then that version will be used if it is a supported version.

4. If the NODE_GYP_FORCE_PYTHON environment variable is set to the path of a Python executable, it will be used instead of any of the other configured or built-in Python search paths. If it's not a compatible version, no further searching will be done.

Build for Third Party Node.js Runtimes

When building modules for third-party Node.js runtimes like Electron, which have different build configurations from the official Node.js distribution, you should use --dist-url or --nodedir flags to specify the headers of the runtime to build for.

Also when --dist-url or --nodedir flags are passed, node-gyp will use the config.gypi shipped in the headers distribution to generate build configurations, which is different from the default mode that would use the process.config object of the running Node.js instance.

Some old versions of Electron shipped malformed config.gypi in their headers distributions, and you might need to pass --force-process-config to node-gyp to work around configuration errors.

How to Use

To compile your native addon first go to its root directory:

cd my_node_addon

The next step is to generate the appropriate project build files for the current platform. Use configure for that:

node-gyp configure

Auto-detection fails for Visual C++ Build Tools 2015, so --msvs_version=2015 needs to be added (not needed when run by npm as configured above):

node-gyp configure --msvs_version=2015

Note: The configure step looks for a binding.gyp file in the current directory to process. See below for instructions on creating a binding.gyp file.

Now you will have either a Makefile (on Unix platforms) or a vcxproj file (on Windows) in the build/ directory. Next, invoke the build command:

node-gyp build

Now you have your compiled .node bindings file! The compiled bindings end up in build/Debug/ or build/Release/, depending on the build mode. At this point, you can require the .node file with Node.js and run your tests!

Note: To create a Debug build of the bindings file, pass the --debug (or -d) switch when running either the configure, build or rebuild commands.

The binding.gyp file

A binding.gyp file describes the configuration to build your module, in a JSON-like format. This file gets placed in the root of your package, alongside package.json.

A barebones gyp file appropriate for building a Node.js addon could look like:

{
  "targets": [
    {
      "target_name": "binding",
      "sources": [ "src/binding.cc" ]
    }
  ]
}

Further reading

The docs directory contains additional documentation on specific node-gyp topics that may be useful if you are experiencing problems installing or building addons using node-gyp.

Some additional resources for Node.js native addons and writing gyp configuration files:

• "Going Native" a nodeschool.io tutorial
• "Hello World" node addon example
• gyp user documentation
• gyp input format reference
• "binding.gyp" files out in the wild wiki page

Commands

node-gyp responds to the following commands:

Command	Description
help	Shows the help dialog
build	Invokes make/msbuild.exe and builds the native addon
clean	Removes the build directory if it exists
configure	Generates project build files for the current platform
rebuild	Runs clean, configure and build all in a row
install	Installs Node.js header files for the given version
list	Lists the currently installed Node.js header versions
remove	Removes the Node.js header files for the given version

Command Options

node-gyp accepts the following command options:

Command	Description
-j n, --jobs n	Run make in parallel. The value max will use all available CPU cores
--target=v6.2.1	Node.js version to build for (default is process.version)
--silly, --loglevel=silly	Log all progress to console
--verbose, --loglevel=verbose	Log most progress to console
--silent, --loglevel=silent	Don't log anything to console
debug, --debug	Make Debug build (default is Release)
--release, --no-debug	Make Release build
-C $dir, --directory=$dir	Run command in different directory
--make=$make	Override make command (e.g. gmake)
--thin=yes	Enable thin static libraries
--arch=$arch	Set target architecture (e.g. ia32)
--tarball=$path	Get headers from a local tarball
--devdir=$path	SDK download directory (default is OS cache directory)
--ensure	Don't reinstall headers if already present
--dist-url=$url	Download header tarball from custom URL
--proxy=$url	Set HTTP(S) proxy for downloading header tarball
--noproxy=$urls	Set urls to ignore proxies when downloading header tarball
--cafile=$cafile	Override default CA chain (to download tarball)
--nodedir=$path	Set the path to the node source code
--python=$path	Set path to the Python binary
--msvs_version=$version	Set Visual Studio version (Windows only)
--solution=$solution	Set Visual Studio Solution version (Windows only)
--force-process-config	Force using runtime's process.config object to generate config.gypi file

Configuration

Environment variables

Use the form npm_config_OPTION_NAME for any of the command options listed above (dashes in option names should be replaced by underscores).

For example, to set devdir equal to /tmp/.gyp, you would:

Run this on Unix:

export npm_config_devdir=/tmp/.gyp

Or this on Windows:

set npm_config_devdir=c:\temp\.gyp

npm configuration for npm versions before v9

Use the form OPTION_NAME for any of the command options listed above.

For example, to set devdir equal to /tmp/.gyp, you would run:

npm config set [--global] devdir /tmp/.gyp

Note: Configuration set via npm will only be used when node-gyp is run via npm, not when node-gyp is run directly.

from https://github.com/nodejs/node-gyp#on-windows