lakutata 3.1.3 → 3.1.5

package/README.md

@@ -19,9 +19,9 @@ English | [中文](README.zh-CN.md)
 # lakutata
 
 An IoC-based application framework for Node.js and TypeScript, with one programming model for web services, CLI tools,
-desktop (Electron) applications and embedded devices. An application is a tree of objects (components, providers,
+desktop (Electron, NW.js) applications and embedded devices. An application is a tree of objects (components, providers,
 controllers) that a container creates. DTOs validate their options and inputs, and transports expose the controllers:
-HTTP (Express, Fastify), CLI (Commander), service RPC (HTTP, Socket.IO, JSON-RPC 2.0, gRPC, NATS, Electron IPC),
+HTTP (Express, Fastify), CLI (Commander), service RPC (HTTP, Socket.IO, JSON-RPC 2.0, gRPC, NATS, Electron IPC, NW.js),
 schedules and message queues. One controller method can serve all of them at once.
 
 This package is the framework itself: it re-exports the `@lakutata/*` packages under the subpaths listed below and
@@ -31,13 +31,13 @@ declaration with examples, and each `@lakutata/*` package has its own README.
 ## Installation
 
 ```shell
-npx @lakutata/cli create --name my-app   # a new project from a template (web, service, CLI, Electron…)
+npx @lakutata/cli create --name my-app   # a new project from a template (web, service, CLI, Electron, NW.js…)
 npm install lakutata                      # or the framework in an existing project
 ```
 
-The framework needs Node.js `^22.13.0 || >=24.11.0`: 22.13 or a later 22.x, or 24.11 and later (not 23). Projects
-use ES modules (`"type": "module"`), as the templates do; the package also ships CommonJS builds. The TypeScript
-options that the framework needs are published as `lakutata/tsconfig.json`:
+The framework needs Node.js 18.10 or later (`>=18.10.0`); a few features need a newer one (see Getting Started).
+Projects use ES modules (`"type": "module"`), as the templates do; the package also ships CommonJS builds. The
+TypeScript options that the framework needs are published as `lakutata/tsconfig.json`:
 
 ```json
 {
@@ -108,7 +108,7 @@ Application
 | `lakutata/decorator/ctrl` | `@lakutata/entrypoint` | `@HTTPAction`, `@GET`…`@OPTIONS`, `@CLIAction`, `@ServiceAction`, `@Schedule`, `@Prefix`, `@UseMiddlewares` |
 | `lakutata/adapter/express`, `lakutata/adapter/fastify` | `@lakutata/entrypoint` | The HTTP transports, `staticUI` (Express only) |
 | `lakutata/adapter/commander` | `@lakutata/entrypoint` | The CLI transport |
-| `lakutata/adapter/socket.io`, `lakutata/adapter/jsonrpc`, `lakutata/adapter/electron` | `@lakutata/entrypoint` | The service transports |
+| `lakutata/adapter/socket.io`, `lakutata/adapter/jsonrpc`, `lakutata/adapter/electron`, `lakutata/adapter/nwjs` | `@lakutata/entrypoint` | The service transports |
 | `lakutata/com/logger` | `@lakutata/logger` | The `Logger` component preset as `log` (pino-compatible JSON lines) |
 | `lakutata/orm`, `lakutata/decorator/orm` | `@lakutata/orm` | TypeORM, its decorators |
 | `lakutata/com/database`, `lakutata/provider/database` | `@lakutata/orm` | The `Database` component and provider, the migration commands |
@@ -144,9 +144,9 @@ on. Each package's README lists its exceptions.
   `Entrypoint.md`, `Middlewares.md`, `HTTP.md`, `CLI.md`, `ServiceCalls.md`, `GRPC.md`, `NATS.md`, `Schedules.md`,
   `Queue.md`, `Database.md`, `DatabaseDrivers.md`, `MongoEmbedded.md`, `Entities.md`, `Migrations.md`, `Cache.md`,
   `Mutex.md`, `I18n.md`, `DockerIntegration.md`, `ContainerdIntegration.md`, `Monitor.md`, `Security.md`, `DBus.md`,
-  `MCP.md`, `WebRTC.md`, `FFI.md`, `Math.md`, `Command.md`, `Workspaces.md`, `NativeAddons.md`, `Packaging.md`,
-  `Installers.md`; and the examples, in `doc/en/examples` and `doc/zh/examples`: whole applications built from the
-  templates.
+  `MCP.md`, `WebRTC.md`, `FFI.md`, `Math.md`, `Netif.md`, `Command.md`, `Workspaces.md`, `NativeAddons.md`,
+  `Packaging.md`, `Installers.md`; and the examples, in `doc/en/examples` and `doc/zh/examples`: whole applications
+  built from the templates.
 - `@lakutata/cli`: creating, building and packaging applications.
 - The official Agent Skill for AI coding assistants that work on lakutata projects:
   [lakutata.com/skill](https://lakutata.com/skill/).

package/README.zh-CN.md

@@ -18,18 +18,18 @@
 
 # lakutata
 
-一个基于 IoC 的 Node.js 和 TypeScript 应用框架，让 Web 服务、命令行工具、桌面（Electron）应用和嵌入式设备共用同一套编程模型。应用是一棵由容器创建的对象树（组件、提供者、控制器）。DTO 校验对象的选项和输入，各种传输方式把控制器暴露出去：HTTP（Express、Fastify）、CLI（Commander）、服务调用（HTTP、Socket.IO、JSON-RPC 2.0、gRPC、NATS、Electron IPC）、定时任务和消息队列。同一个控制器方法可以同时通过所有这些方式调用。
+一个基于 IoC 的 Node.js 和 TypeScript 应用框架，让 Web 服务、命令行工具、桌面（Electron、NW.js）应用和嵌入式设备共用同一套编程模型。应用是一棵由容器创建的对象树（组件、提供者、控制器）。DTO 校验对象的选项和输入，各种传输方式把控制器暴露出去：HTTP（Express、Fastify）、CLI（Commander）、服务调用（HTTP、Socket.IO、JSON-RPC 2.0、gRPC、NATS、Electron IPC、NW.js）、定时任务和消息队列。同一个控制器方法可以同时通过所有这些方式调用。
 
 这个包就是框架本身：它通过下面列出的子路径重新导出各个 `@lakutata/*` 包，并为每个应用预置两个组件：`log` 和 `entrypoint`。各子路径的类型声明中，每一项都附有说明和示例，每个 `@lakutata/*` 包也都有自己的 README。
 
 ## 安装
 
 ```shell
-npx @lakutata/cli create --name my-app   # 用模板创建新项目（Web、服务、CLI、Electron……）
+npx @lakutata/cli create --name my-app   # 用模板创建新项目（Web、服务、CLI、Electron、NW.js……）
 npm install lakutata                      # 或者在已有项目中安装框架
 ```
 
-框架需要 Node.js `^22.13.0 || >=24.11.0`：22.13 或更高的 22.x 版本，或者 24.11 及以上（不支持 23）。项目使用 ES 模块（`"type": "module"`），模板也是如此；这个包也提供 CommonJS 版本。框架需要的 TypeScript 选项发布为 `lakutata/tsconfig.json`：
+框架需要 Node.js 18.10 或更高版本（`>=18.10.0`），少数功能需要较新的版本（见快速开始）。项目使用 ES 模块（`"type": "module"`），模板也是如此；这个包也提供 CommonJS 版本。框架需要的 TypeScript 选项发布为 `lakutata/tsconfig.json`：
 
 ```json
 {
@@ -97,7 +97,7 @@ Application
 | `lakutata/decorator/ctrl` | `@lakutata/entrypoint` | `@HTTPAction`、`@GET`…`@OPTIONS`、`@CLIAction`、`@ServiceAction`、`@Schedule`、`@Prefix`、`@UseMiddlewares` |
 | `lakutata/adapter/express`、`lakutata/adapter/fastify` | `@lakutata/entrypoint` | HTTP 传输、`staticUI`（仅 Express） |
 | `lakutata/adapter/commander` | `@lakutata/entrypoint` | CLI 传输 |
-| `lakutata/adapter/socket.io`、`lakutata/adapter/jsonrpc`、`lakutata/adapter/electron` | `@lakutata/entrypoint` | 服务传输 |
+| `lakutata/adapter/socket.io`、`lakutata/adapter/jsonrpc`、`lakutata/adapter/electron`、`lakutata/adapter/nwjs` | `@lakutata/entrypoint` | 服务传输 |
 | `lakutata/com/logger` | `@lakutata/logger` | `Logger` 组件，预置为 `log`（输出与 pino 兼容的 JSON 行） |
 | `lakutata/orm`、`lakutata/decorator/orm` | `@lakutata/orm` | TypeORM 及其装饰器 |
 | `lakutata/com/database`、`lakutata/provider/database` | `@lakutata/orm` | `Database` 组件和提供者、迁移命令 |
@@ -121,7 +121,7 @@ Application
 ## 另见
 
 - 网站 <https://lakutata.com/zh/>：指南、示例和 API 参考，中英文都有。
-- 指南在这个包的 `doc/zh`（中文）和 `doc/en`（英文）中：`Overview.md`、`GettingStarted.md`、`ProjectStructure.md`、`UpgradingFrom2.md`、`UpgradingFrom1.md`、`Application.md`、`Objects.md`、`Injection.md`、`DTOValidation.md`、`Exceptions.md`、`Logger.md`、`Decorator.md`、`Time.md`、`HelperFunctions.md`、`Controllers.md`、`Entrypoint.md`、`Middlewares.md`、`HTTP.md`、`CLI.md`、`ServiceCalls.md`、`GRPC.md`、`NATS.md`、`Schedules.md`、`Queue.md`、`Database.md`、`DatabaseDrivers.md`、`MongoEmbedded.md`、`Entities.md`、`Migrations.md`、`Cache.md`、`Mutex.md`、`I18n.md`、`DockerIntegration.md`、`ContainerdIntegration.md`、`Monitor.md`、`Security.md`、`DBus.md`、`MCP.md`、`WebRTC.md`、`FFI.md`、`Math.md`、`Command.md`、`Workspaces.md`、`NativeAddons.md`、`Packaging.md`、`Installers.md`；示例在 `doc/zh/examples` 和 `doc/en/examples` 中：从模板构建的完整应用。
+- 指南在这个包的 `doc/zh`（中文）和 `doc/en`（英文）中：`Overview.md`、`GettingStarted.md`、`ProjectStructure.md`、`UpgradingFrom2.md`、`UpgradingFrom1.md`、`Application.md`、`Objects.md`、`Injection.md`、`DTOValidation.md`、`Exceptions.md`、`Logger.md`、`Decorator.md`、`Time.md`、`HelperFunctions.md`、`Controllers.md`、`Entrypoint.md`、`Middlewares.md`、`HTTP.md`、`CLI.md`、`ServiceCalls.md`、`GRPC.md`、`NATS.md`、`Schedules.md`、`Queue.md`、`Database.md`、`DatabaseDrivers.md`、`MongoEmbedded.md`、`Entities.md`、`Migrations.md`、`Cache.md`、`Mutex.md`、`I18n.md`、`DockerIntegration.md`、`ContainerdIntegration.md`、`Monitor.md`、`Security.md`、`DBus.md`、`MCP.md`、`WebRTC.md`、`FFI.md`、`Math.md`、`Netif.md`、`Command.md`、`Workspaces.md`、`NativeAddons.md`、`Packaging.md`、`Installers.md`；示例在 `doc/zh/examples` 和 `doc/en/examples` 中：从模板构建的完整应用。
 - `@lakutata/cli`：创建、构建和打包应用。
 - 官方 Agent Skill（智能体技能），供 AI 编程助手在 lakutata 项目中使用：<https://lakutata.com/zh/skill/>。
 

package/dist/cjs/exports/NwjsAdapter.d.ts

@@ -0,0 +1 @@
+export * from '@lakutata/entrypoint/adapter/nwjs';

package/dist/cjs/exports/NwjsAdapter.js

@@ -0,0 +1,20 @@
+"use strict";
+var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    var desc = Object.getOwnPropertyDescriptor(m, k);
+    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
+      desc = { enumerable: true, get: function() { return m[k]; } };
+    }
+    Object.defineProperty(o, k2, desc);
+}) : (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    o[k2] = m[k];
+}));
+var __exportStar = (this && this.__exportStar) || function(m, exports) {
+    for (var p in m) if (p !== "default" && !Object.prototype.hasOwnProperty.call(exports, p)) __createBinding(exports, m, p);
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+__exportStar(require("@lakutata/entrypoint/adapter/nwjs"), exports);
+
+//The default of the entry: the entry itself (scripts/package-build/cjs-package.mjs)
+if (!Object.prototype.hasOwnProperty.call(exports, 'default')) Object.defineProperty(exports, 'default', {value: exports})

package/dist/esm/exports/NwjsAdapter.js

@@ -0,0 +1 @@
+export * from '@lakutata/entrypoint/adapter/nwjs';

package/dist/types/exports/NwjsAdapter.d.ts

@@ -0,0 +1 @@
+export * from '@lakutata/entrypoint/adapter/nwjs';

package/doc/en/Application.md

@@ -12,7 +12,7 @@ options:
 
 | Option | Meaning |
 |---|---|
-| `id`, `name` | Required. The ID (also the `process.title`) and the name of the application (`app.appId`, `app.appName`) |
+| `id`, `name` | Required. The ID (also the `process.title`, except in NW.js) and the name of the application (`app.appId`, `app.appName`) |
 | `timezone` | An IANA time zone, or `'auto'` (default) for the system's; written to `TZ` |
 | `mode` | `'development'` or `'production'`, when the environment gives none (see section 4) |
 | `shutdownSignals` | The signals that end the application gracefully (default `['SIGTERM', 'SIGINT']`), or `false` |

package/doc/en/Cache.md

@@ -290,7 +290,8 @@ The values are kept as they are, not copied (section 7). Each process has its ow
 - The statements run synchronously: a statement that waits for a locked database blocks the event loop, up to
   `busyTimeout`.
 - `better-sqlite3` is a native addon built for one runtime: an Electron application needs its build for its version of
-  Electron. On Bun, the store uses `bun:sqlite` instead.
+  Electron; an NW.js application has it built again with the headers of NW.js (0.111.3 or later: the earlier releases
+  cannot load it). On Bun, the store uses `bun:sqlite` instead.
 
 ### PostgreSQL
 

package/doc/en/Command.md

@@ -13,8 +13,7 @@ npm install --global @lakutata/cli         # or once for the machine, then: laku
 ```
 
 The templates add `@lakutata/cli` to the `devDependencies` of the project, so its scripts call `lakutata` directly and
-`npx lakutata` works inside it. The tool needs Node.js `^22.13.0 || >=24.11.0`: 22.13 or a later 22.x, or 24.11 and
-later (not 23).
+`npx lakutata` works inside it. The tool needs Node.js 18.10 or later (`>=18.10.0`).
 
 - `lakutata --help` lists the commands, `lakutata help <command>` (or `lakutata <command> --help`) describes one, and
   `lakutata --version` prints the version of the tool. Without a command, the tool prints its help and exits with code
@@ -46,7 +45,7 @@ lakutata create --name tool --template cli --package-manager none --no-git
 | `--path` | `.` | Where the project directory is created (`<path>/<name>`) |
 | `--init` | | Create the project in `--path` itself, a directory that already exists |
 | `--description`, `--author`, `--license` | license `UNLICENSED` | The information of the package |
-| `--with` | | The optional features of the template, separated by commas (`i18n`, `installer`) |
+| `--with` | | The optional features of the template, separated by commas (`i18n`, `installer`, `win7`) |
 | `--package-manager` | `npm`, or pnpm or yarn when one of them started the tool | `npm`, `pnpm`, `yarn`, or `none` to skip the installation |
 | `--no-git` | | Do not create a git repository |
 | `--yes` | | Do not ask for the features or for a confirmation |
@@ -99,6 +98,11 @@ adds a language. See [I18n](I18n.md#command-line-tools).
 that runs without Node.js: see [Packaging](Packaging.md). `lakutata package installer` makes its installers, which can
 register it as a service: see [Installers](Installers.md).
 
+An NW.js application gets its version of NW.js from `lakutata nwjs use <version>` (`latest`, `win7` or a version, which
+`lakutata nwjs versions` lists), which writes it into its `package.json`. `lakutata nwjs run [args...]` runs the compiled
+application in the sdk flavor of that NW.js (with the DevTools), its native addons made to load in it, and gives it the
+arguments. Its installers hold the normal flavor ([Installers](Installers.md), section 9).
+
 ## 6. Environment variables
 
 | Variable | Meaning |
@@ -106,7 +110,9 @@ register it as a service: see [Installers](Installers.md).
 | `LAKUTATA_LANG` | The language of the tool (`en`, `zh-CN`, `zh-TW`) |
 | `LAKUTATA_NPM_REGISTRY` | The registry the templates come from (else `npm_config_registry`, else `https://registry.npmjs.org`) |
 | `LAKUTATA_GITHUB_DOWNLOAD` | Where the `github:` templates are downloaded from (`https://github.com` by default) |
-| `LAKUTATA_CACHE_DIR` | The cache of the tool: the templates, and the tools that make installers (`$XDG_CACHE_HOME/lakutata`, else `~/.cache/lakutata`) |
+| `LAKUTATA_CACHE_DIR` | The cache of the tool: the templates, the tools that make installers and the runtimes of NW.js (`$XDG_CACHE_HOME/lakutata`, else `~/.cache/lakutata`) |
+| `LAKUTATA_NWJS_MIRROR` | Where the runtimes of NW.js are downloaded from (`https://dl.nwjs.io` by default) |
+| `LAKUTATA_NWJS_VERSIONS` | The list of the releases of NW.js (`https://nwjs.io/versions.json` by default) |
 | `NO_COLOR` | Turns the colors off |
 
 The scripts and the applications the tool runs get the environment the tool was started with. The variables of the

package/doc/en/ContainerdIntegration.md

@@ -15,7 +15,7 @@ The containers it creates are the same as the containers nerdctl creates: they c
 
 | Feature | Needs |
 |---|---|
-| Everything | Linux, containerd 1.6 or later with runc, Node.js `^22.13.0 || >=24.11.0`; the application runs as root or as a member of the group owning the socket of containerd |
+| Everything | Linux, containerd 1.6 or later with runc, Node.js `>=18.10.0`; the application runs as root or as a member of the group owning the socket of containerd |
 | CNI networks (the default `bridge` included), published ports | The CNI plugins (`bridge`, `portmap`, `host-local`… in `/opt/cni/bin`, `/usr/lib/cni` or `/usr/libexec/cni`, the `cniPath` option) and iptables |
 | `exec()` with `stdin`, separate `stdout`/`stderr`, terminals | `mkfifo` on the host (without it, `exec()` puts both outputs in `stdout`) |
 | Builds | A BuildKit daemon (`buildkitd`), local or remote |

package/doc/en/DatabaseDrivers.md

@@ -136,8 +136,9 @@ export const db = buildDatabaseOptions({
 - The foreign keys are enforced (`PRAGMA foreign_keys = ON`). There is one connection: `poolSize` is not supported.
 - **`bigint` columns come back as numbers**: values beyond 2^53 lose precision. Keep such values in a text column.
 - `better-sqlite3` is a native module, compiled for one version of Node.js. An Electron application needs the build of
-  its Electron (`electron-rebuild`, or the prebuilt binaries of better-sqlite3 for Electron); Bun cannot load it (use
-  `sqljs` there).
+  its Electron (`electron-rebuild`, or the prebuilt binaries of better-sqlite3 for Electron); an NW.js application has
+  it built again with the headers of NW.js (0.111.3 or later: use `sqljs` with the earlier releases); Bun cannot load it
+  (use `sqljs` there).
 
 ## SQLite: sql.js
 

package/doc/en/Entrypoint.md

@@ -60,6 +60,7 @@ The adapters:
 | `service` | `socketIOServiceEntrypoint()` | `lakutata/adapter/socket.io` | `socket.io` | [ServiceCalls](ServiceCalls.md) |
 | `service` | `jsonRPCServiceEntrypoint()` | `lakutata/adapter/jsonrpc` | `ws`, for WebSocket | [ServiceCalls](ServiceCalls.md) |
 | `service` | `electronIPCServiceEntrypoint()` | `lakutata/adapter/electron` | (Electron) | [ServiceCalls](ServiceCalls.md) |
+| `service` | `nwjsServiceEntrypoint()` | `lakutata/adapter/nwjs` | (NW.js) | [ServiceCalls](ServiceCalls.md) |
 | `service` | `grpcServiceEntrypoint()` | `@lakutata/grpc/service` | `@lakutata/grpc` | [GRPC](GRPC.md) |
 | `service` | `natsServiceEntrypoint()` | `@lakutata/nats` | `@lakutata/nats` | [NATS](NATS.md) |
 | `schedule` | `scheduleEntrypoint()` | `lakutata/com/entrypoint` | | [Schedules](Schedules.md) |
@@ -181,8 +182,8 @@ actions of any other transport (`getActions('schedule')`). Each action is descri
 
 ## 6. Pushing events to the clients
 
-The service transports that keep their clients connected (Socket.IO, Electron, the event stream of the HTTP service,
-JSON-RPC over WebSocket or stdio, gRPC) can receive events from the application.
+The service transports that keep their clients connected (Socket.IO, Electron, NW.js, the event stream of the HTTP
+service, JSON-RPC over WebSocket or stdio, gRPC) can receive events from the application.
 `entrypoint.notify(clientId, event, ...args)` sends an event to the client whose id an action found in
 `this.context.clientId`, and returns whether that client received it. `entrypoint.broadcast(event, ...args)` sends it to
 every connected client, and returns their number. See [GRPC](GRPC.md) and [ServiceCalls](ServiceCalls.md).

package/doc/en/Exceptions.md

@@ -121,7 +121,7 @@ When an action fails, its transport reports the exception:
 | Transport | The client receives |
 |---|---|
 | HTTP | The status `statusCode` and `{errno, errMsg}` (see [HTTP](HTTP.md), section 6) |
-| Socket.IO, Electron, the HTTP service, NATS, gRPC | The whole error: all its own properties (see [ServiceCalls](ServiceCalls.md), section 3) |
+| Socket.IO, Electron, NW.js, the HTTP service, NATS, gRPC | The whole error: all its own properties (see [ServiceCalls](ServiceCalls.md), section 3) |
 | JSON-RPC | An error with the code `-32602` for an invalid input, `-32601` when no action matches, `-32001` while the application stops, `-32000` otherwise, and the whole error as its `data` |
 | The command line | `error: <message>` on the standard error, and the exit code 1 (see [CLI](CLI.md)) |
 | Schedules | No client: the exception is given to `onError`, or logged (see [Schedules](Schedules.md)) |

package/doc/en/FFI.md

@@ -433,7 +433,7 @@ Stopping a worker while asynchronous calls run in the threads of its libraries d
 
 ## 12. Runtimes
 
-Node.js `^22.13.0 || >=24.11.0`, the main process of Electron and Bun; not the renderers of Electron nor the browsers.
+Node.js `>=18.10.0`, the main process of Electron and Bun; not the renderers of Electron nor the browsers.
 
 The tests of the package, including those of the threads of a library, pass on macOS (arm64: Node.js 24, Bun 1.4,
 Electron 44), on Linux (arm64, glibc and musl: Node.js 24, Bun 1.4) and on Windows 11 (arm64, and x64 under emulation:

package/doc/en/GRPC.md

@@ -2,7 +2,7 @@
 
 The package `@lakutata/grpc` serves the service actions of an application over gRPC, and calls them from another
 application. Any language with a gRPC library can call them too. It is written in TypeScript over the HTTP/2 module of
-Node.js (`^22.13.0 || >=24.11.0`): no native addon and no generated code. `lakutata` does not include it, so install it
+Node.js (`>=18.10.0`): no native addon and no generated code. `lakutata` does not include it, so install it
 next to it:
 
 ```bash
@@ -56,10 +56,15 @@ The options of `grpcServiceEntrypoint`:
 | `tls` | None (plain HTTP/2) | `{cert, key}` for TLS; with `ca` too, the clients must present a certificate signed by it (mutual TLS) |
 | `maxMessageSize` | 4 MiB | The largest request, before and after decompression; a larger one fails with `RESOURCE_EXHAUSTED` |
 | `compression` | `'identity'` | `'gzip'` or `'deflate'` to compress the responses for the clients that accept it. Compressed requests are always accepted |
-| `listening` | | `(address) => void`, called once the server listens; the start waits for it |
+| `listening` | | `(address, listeners) => void`, called once the server listens; the start waits for it |
+| `interface`, `family`, `strict`, `onError` | | Listen on a network interface instead of an address, as the HTTP adapters do (see [HTTP](HTTP.md), section 2); not with `host` or `socketPath` |
 | `middlewares` | | The middlewares of the actions called over gRPC, run after the ones of the entrypoint |
 | `name` | | The name of the adapter, to tell several apart |
 
+With `interface`, the package `@lakutata/netif` has to be installed. The `address` given to `listening` is then the
+first one listened on, or `null` while the interface does not exist or has no address yet, and `listeners` are the
+listeners of the interface.
+
 The server has no reflection service and no health service.
 
 ## 2. Calling them from another application
@@ -248,4 +253,5 @@ seconds by default) to complete. Then the event streams end and the server close
 
 The package also has the layers the service is built on, usable without lakutata: `GRPCConnection`, a client for any
 gRPC server (unary, server streaming and bidirectional calls, metadata, TLS); `GRPCServer`; and `encode`/`decode`, a
-protobuf codec driven by schemas. The README of `@lakutata/grpc` describes them.
+protobuf codec driven by schemas. The README of `@lakutata/grpc` describes them. `GRPCServer.listenWith()` listens
+through the listeners of network interfaces (`listenOnAll()` of `@lakutata/netif`), as the adapter does.

package/doc/en/GettingStarted.md

@@ -5,7 +5,18 @@ and write an application by hand.
 
 ## 1. Requirements
 
-- Node.js `^22.13.0 || >=24.11.0`: 22.13 or a later 22.x, or 24.11 and later (not 23).
+- Node.js 18.10 or later (`>=18.10.0`). A few features need a newer Node.js:
+  - the Fastify adapter: Fastify 5 needs Node.js 18.19, 19.9, 20 or later (the Express adapter needs nothing more);
+  - the Kafka transport of `@lakutata/queue`: Node.js 22.22, 24.6 or later, as `@platformatic/kafka` needs;
+  - the executables of Node.js (`lakutata package exe`, the installers): made by a Node.js 20.12, 21.7 or later, or with
+    `--node-program` naming one;
+  - `await using` with the objects of the framework: Node.js 18.18, 20.4 or later.
+
+  On Node.js 18 and 19, an application uses commander 13, @inquirer/prompts 7 and better-sqlite3 11: their next major
+  versions need Node.js 20 or later.
+
+  The projects made by `lakutata create` declare Node.js `>=22.13.0`, which the tools of the web and desktop templates
+  need.
 - TypeScript, with its decorators (`experimentalDecorators`) and their metadata (`emitDecoratorMetadata`). The framework
   publishes the compiler options it needs as `lakutata/tsconfig.json`; the templates use TypeScript 6.
 - ES modules (`"type": "module"`), as in the templates; the package also ships CommonJS builds.
@@ -36,13 +47,15 @@ The `default` template is a small HTTP application. Other templates start from a
 | `web-react`, `web-vue` | An HTTP API serving a React or Vue single-page application (Vite) |
 | `web-next`, `web-nuxt` | An HTTP API serving a Next.js or Nuxt application from the same process |
 | `electron-react`, `electron-vue` | A desktop application: Electron, its main process serving a React or Vue renderer over IPC |
+| `nwjs-react`, `nwjs-vue` | A desktop application: NW.js, its background script serving a React or Vue user interface isolated in a webview |
 
 ```bash
 npx @lakutata/cli create --name shop --template service --with i18n,installer
 ```
 
 `--with` adds optional features: `i18n` (messages in several languages) to every template, `installer` (installers
-and a system service) to `cli`, `service` and the `web-*` templates. In a terminal, the tool offers them when `--with`
+and a system service) to `cli`, `service` and the `web-*` templates, `win7` (NW.js 0.72, which runs on Windows 7) to
+the `nwjs-*` templates. In a terminal, the tool offers them when `--with`
 is not given. [ProjectStructure](ProjectStructure.md) describes the files of the templates, and
 [Command](Command.md) the options of `lakutata create`.
 

package/doc/en/HTTP.md

@@ -105,6 +105,7 @@ Both adapters serve the same actions, with the same results:
 |---|---|---|
 | Adapter | `expressHTTPEntrypoint()`, from `lakutata/adapter/express` | `fastifyHTTPEntrypoint()`, from `lakutata/adapter/fastify` |
 | Install | `express` (4 or 5) | `fastify` (5) |
+| Node.js | 18.10 and later | 18.19, 19.9, 20 and later (Fastify 5 needs `diagnostics_channel.tracingChannel`) |
 
 The options of `expressHTTPEntrypoint()`:
 
@@ -123,6 +124,8 @@ The options of `expressHTTPEntrypoint()`:
 | `fallback` | | Answers the requests outside the paths of the actions, such as the pages of a web UI (section 7) |
 | `stop` | | Called when the adapter stops, once its server is closed |
 | `heartbeat` | `15000` | How often a comment keeps the event streams alive, in milliseconds (section 5) |
+| `listening` | | `(server, listeners) => …`: called once the server listens, or once the listeners of the interface are made (see below) |
+| `interface` | | The network interface to listen on instead of an address, with `family`, `strict` and `onError` (see below) |
 
 `fastifyHTTPEntrypoint()` takes the same options, except `server` and `app`, replaced by `fastify`: a Fastify instance,
 or the options of the instance to create (`bodyLimit`, 1 MiB by default; `trustProxy`; `connectionTimeout`,
@@ -146,6 +149,38 @@ the event streams; Fastify also answers 503 to the requests that still arrive on
 progress get the `shutdownTimeout` of the entrypoint (after it, they are answered with 503), then up to one second to
 send their responses, before the remaining connections are closed, the WebSockets included.
 
+### On a network interface
+
+A device with several network interfaces often serves its pages on one of them only, and the address of that interface
+comes from DHCP and changes. With `interface`, the adapter listens on the interface instead of an address, whatever its
+addresses, and goes on listening when they change and when the interface is unplugged and plugged back. By default it
+uses the package `@lakutata/netif`, installed apart, which compiles a native addon (see [Netif](Netif.md)).
+
+```typescript
+import {expressHTTPEntrypoint} from 'lakutata/adapter/express'
+
+//The pages on eth1 only, whatever its address
+export const http = expressHTTPEntrypoint({
+    port: 8080,
+    interface: 'eth1',
+    listening: (_server, listeners): void => console.log(listeners?.map(listener => listener.addresses))
+})
+```
+
+| Option | Default | Meaning |
+|---|---|---|
+| `interface` | | The name of the interface (`'eth1'`; on Windows the name of the network connection), `{mac: '52:54:00:12:34:56'}` or `{index: 3}`; several in an array, and then `port` cannot be `0`. It cannot be given with `host` |
+| `family` | `'both'` | `'IPv4'`, `'IPv6'` or both |
+| `strict` | `false` | Fails the start where the system cannot refuse the connections that reach the addresses of the interface through another interface, and stops listening while it cannot (see [Netif](Netif.md), section 2) |
+| `onError` | the log of the application | Receives the errors of listening again while the application runs, such as a port taken by another program; the adapter retries by itself |
+| `interfaceListening` | `@lakutata/netif` | Another implementation of the listening on interfaces: an `IInterfaceListening`, the contract of lakutata that `@lakutata/netif` implements |
+
+- The interface may not exist yet when the application starts (a USB network adapter not plugged in): the start
+  succeeds, and the adapter listens once the interface appears. Until then the `addresses` of the listeners are empty.
+- The server itself does not listen, and its `address()` is `null`: the listeners give the port and the addresses.
+- `family`, `strict`, `onError` and `interfaceListening` without `interface` fail the creation of the adapter, as do
+  `interface` and `host` together.
+
 ## 3. Routes
 
 | Decorator | Methods |

package/doc/en/I18n.md

@@ -174,7 +174,7 @@ The languages a request asks for are read from the sources below, in order, then
 | HTTP (Express, Fastify) | The query parameter `?lang=`, the cookie `lang`, then the `Accept-Language` header (by quality) |
 | Socket.IO | The query parameter `lang`, the cookie `lang` and `Accept-Language` of the connection's handshake |
 | HTTP service adapter, JSON-RPC (HTTP, WebSocket) | The query parameter `lang`, the cookie `lang` and `Accept-Language` of the HTTP request (for WebSocket, of the request opening the connection) |
-| Command line, Electron IPC, JSON-RPC over stdio | The variable named by `environmentVariable` (none by default), `LANGUAGE`, `LC_ALL`, `LC_MESSAGES`, `LANG`, then the language of the process |
+| Command line, Electron IPC, NW.js, JSON-RPC over stdio | The variable named by `environmentVariable` (none by default), `LANGUAGE`, `LC_ALL`, `LC_MESSAGES`, `LANG`, then the language of the process |
 | Schedules | None (the default language) |
 
 A query or cookie value that is not a language tag is skipped.

package/doc/en/Installers.md

@@ -21,7 +21,8 @@ npx lakutata package installer --target pkg     # only some of them
 
 An installer holds the executable of the directory layout (`lakutata package exe --layout directory`): the program,
 its native addons (`native/`) and its resources (`resources/`). The program is made with Node.js, or with Bun when
-`lakutata.installer.runtime` is `"bun"`.
+`lakutata.installer.runtime` is `"bun"`. On a Node.js older than 20.12, give a newer one with `--node-program`, as for
+the executables.
 
 | Platform | Installers (default) | Their files | Made with |
 |---|---|---|---|
@@ -68,19 +69,19 @@ The installers are configured by `lakutata.installer` in the `package.json` of t
 | `description`, `homepage`, `license` | Those of the `package.json` | The information of the packages |
 | `maintainer` | The `author` of the `package.json` | Its maintainer (`Name <email>`); without one, the tool warns |
 | `vendor` | None | Its vendor; on Windows, the publisher is the vendor, else the maintainer |
-| `runtime` | `node` | `node` or `bun` for the executable; `electron` for an Electron application (section 8) |
+| `runtime` | `node` | `node` or `bun` for the executable; `electron` for an Electron application (section 8), `nwjs` for an NW.js application (section 9) |
 | `addToPath` | `true` | Put the program in the PATH: `/usr/bin/<program>` on Linux, `/usr/local/bin/<program>` on macOS, the PATH of the machine on Windows |
 | `service` | None | `true`, or the options of the service (section 4) |
 | `linux.targets` | `deb`, `rpm`, `tar.gz`; on Alpine `apk`, `tar.gz` | The Linux installers (`deb`, `rpm`, `archlinux`, `tar.gz`; `apk`, `tar.gz` on Alpine) |
 | `linux.depends`, `linux.recommends` | None | The system packages it needs and recommends (the C++ runtime library is always added) |
 | `linux.section`, `linux.priority` | None | Its section and its priority (deb) |
-| `mac.targets` | `pkg`, `tar.gz` | The macOS installers |
+| `mac.targets` | `pkg`, `tar.gz` | The macOS installers (`dmg` too, for an NW.js application) |
 | `win.targets` | `nsis`, `msi`, `zip` | The Windows installers |
 | `linux.scripts`, `mac.scripts`, `win.scripts`… | None | The scripts of the installers (section 5) |
 | `electron` | None | The configuration of electron-builder (section 8) |
 
 `lakutata.icon` (beside `lakutata.installer`) is a square PNG image of 256 pixels or more: the icon of the Windows
-executable and installers, and of the Electron applications.
+executable and installers, and of the Electron and NW.js applications.
 
 The configuration is checked before anything is built, the options of the installers that are not made included, and an
 error names the field:
@@ -202,8 +203,9 @@ fi
 
 ## 6. Signing
 
-- **macOS**: the `pkg` installers are not signed, and the program they install is signed ad hoc only. The Developer ID
-  signature and the notarization, which distribution outside the machines of the organization needs, are not made yet.
+- **macOS**: the `pkg` installers and the `dmg` images are not signed, and the program or the application they install
+  is signed ad hoc only. The Developer ID signature and the notarization, which distribution outside the machines of the
+  organization needs, are not made yet.
 - **Windows**: the NSIS and MSI installers are not signed: sign them with signtool before distributing them. The program
   made with Node.js keeps the signature of `node.exe`, which no longer matches, and the tool warns of it.
 - **Linux**: the packages are not signed.
@@ -278,3 +280,29 @@ and `electron-vue` templates are configured this way.
   ([NativeAddons](NativeAddons.md), section 4).
 - On Linux arm64, the deb and rpm packages need the fpm of the system (`gem install fpm`, `USE_SYSTEM_FPM=true`), as the
   `Dockerfile.installer` of the Electron templates installs it.
+
+## 9. NW.js applications
+
+With `"runtime": "nwjs"`, the installers hold an NW.js application made by the builder: the normal flavor of the NW.js
+of the application (its `lakutata.nwjs`, given by `lakutata nwjs use`), downloaded once into the cache of lakutata and
+checked against the checksums of its release, with the application in it: its bundle for the Node.js of that NW.js, its
+native addons, its resources (`lakutata.resources`, read through `resourcesPath()`) and the manifest of NW.js. The
+`nwjs-react` and `nwjs-vue` templates are configured this way.
+
+- **The runtime** is named after the application: on Windows, `<name>.exe`, whose icon and version information are
+  those of the application; on Linux, `<name>`; on macOS, `<productName>.app`, whose `Info.plist` gives its name, its
+  identifier (`appId`), its version and its icon, and which is signed again ad hoc.
+- **The installers** are those of a desktop application: `dmg` on macOS, `nsis` on Windows and `deb` on Linux by
+  default (also `pkg` and `tar.gz` on macOS, `msi` and `zip` on Windows, `rpm` and `tar.gz` on Linux). The Windows
+  installers add the application to the start menu and to the desktop; the `dmg` disk image holds it beside a link to
+  /Applications, where its user drags it, and the `pkg` package installs it there (an Intel application, on the Macs
+  of Apple silicon too); the Linux packages add its desktop entry and its icons, and depend on the libraries of
+  Chromium.
+- **The architecture** is the one of the machine, or the one of `--arch` (`x64`, `ia32`, `arm64`): `ia32` makes the
+  installers of 32-bit Windows, which install the application among the programs of 32 bits. A release of NW.js
+  without a build for the Macs of Apple silicon (0.72) is packaged for Intel.
+- **An NW.js application is not a service**, and is not put in the PATH (`addToPath` is `false` by default).
+- **The scripts** run as for the other applications, but a macOS application is removed by deleting it: no removal
+  script runs there.
+- **Native addons** are made to load in NW.js: built again for its architecture, or with its headers when they use the
+  V8 API, and, on Windows, given the Node.js of NW.js ([NativeAddons](NativeAddons.md), section 4).

package/doc/en/MCP.md

@@ -248,7 +248,8 @@ Application.run(() => ({
 |---|---|---|
 | `port`, `host`, `path` | `3000`, `'127.0.0.1'`, `'/mcp'` | Where it listens |
 | `authenticate` | | `(request) => MCPAuthInfo \| undefined`: the authentication of the client; throwing answers 401, returning `undefined` serves the request without one |
-| `allowedHosts`, `allowedOrigins` | the local names, on a local address | The `Host` and `Origin` headers accepted (403 otherwise); `false` checks none |
+| `allowedHosts`, `allowedOrigins` | the local names, on a local address or the loopback interface | The `Host` and `Origin` headers accepted (403 otherwise); `false` checks none |
+| `interface`, `family`, `strict`, `onError` | | Listen on a network interface instead of `host`, with the package `@lakutata/netif` (see [HTTP](HTTP.md), section 2) |
 | `legacy` | `'stateless'` | The clients of the revisions of 2025: served without sessions, or refused with `'reject'` |
 | `maxRequestBodySize` | 4 MiB | A larger body is answered with 413 |
 | `bus` | in memory | Where the notifications go, to share them between the instances of the application |
@@ -258,7 +259,8 @@ Application.run(() => ({
 - It serves the protocol over Streamable HTTP: the revision 2026-07-28, and the revisions of 2025 without sessions.
 - On a local address, the `Host` and `Origin` headers are checked against the local names, which protects the server
   from DNS rebinding: behind a proxy, list the names the clients use. On another address, nothing is checked unless you
-  list names.
+  list names. The same goes for `interface`: the loopback interface is checked against the local names, and on another
+  interface the clients of the network reach the server, so set `allowedHosts` and `authenticate`.
 - When the application stops, the calls in progress are answered, then the port closes.
 
 **Sharing the port of the HTTP adapter.** With `listen: false`, mount the `handler` of the adapter on the Express

package/doc/en/Math.md

@@ -348,7 +348,7 @@ $ curl -X POST localhost:8080/solve -H 'Content-Type: application/json' -d '{"eq
 - The bundles, the executables and the installers made by `lakutata package` carry the compiled addon
   (`build/Release/math.node`). Build them on each target platform, after installing the package there; the rules of
   the native addons apply (see [Packaging](Packaging.md) and [NativeAddons](NativeAddons.md)).
-- The package runs in Node.js `^22.13.0 || >=24.11.0`, in Bun and in the main process of Electron, which load the
+- The package runs in Node.js `>=18.10.0`, in Bun and in the main process of Electron, which load the
   addon compiled for Node.js; not in the renderers of Electron nor in the browsers. In Bun, terminating a worker thread
   while operations of the addon still run in it ends the whole process with a fatal error of Node-API (a bug of Bun
   1.4).

package/doc/en/NativeAddons.md

@@ -66,14 +66,13 @@ And `src/index.ts`, the same for all three:
 ```typescript
 import {createRequire} from 'node:module'
 import path from 'node:path'
-import {fileURLToPath} from 'node:url'
 
 type Binding = {
     greet(name: string): string
 }
 
 /** The addon built into build/Release, loaded from the directory of the package */
-const binding: Binding = createRequire(import.meta.url)('node-gyp-build')(path.resolve(path.dirname(fileURLToPath(import.meta.url)), '..'))
+const binding: Binding = createRequire(__filename)('node-gyp-build')(path.resolve(__dirname, '..'))
 
 export function greet(name: string): string {
     return binding.greet(name)
@@ -96,6 +95,8 @@ export function greet(name: string): string {
   for the architecture of the machine (`rustup target add` adds the other ones).
 - **Node-API**: the addons are built for Node-API version 8, which every supported version of Node.js and of Electron
   provides, so they are not rebuilt for each of them.
+- **CommonJS**: the package is CommonJS (`"type": "commonjs"`). The bundles of `lakutata package` are CommonJS and
+  load it with `require`, which can load an ES module only on Node.js 20.19, 22.12 or later.
 - The package is `"private": true`, like every package that `lakutata add` creates: an addon is usually shipped with
   its application rather than published.
 
@@ -214,5 +215,11 @@ The application depends on the addon package, and imports it as any package (`im
 - **Electron**: the addons are copied as they are installed. The addons that `lakutata add` creates run in Electron
   without being rebuilt, as do all the addons built on Node-API; an addon built on the V8 API of Node.js must be
   installed in its build for Electron before packing (`electron-rebuild`).
+- **NW.js**: the addons are made to load in NW.js when the application runs in it (`lakutata nwjs run`, and once
+  packaged). The ones built for another architecture than the one of the runtime are built again from their sources,
+  with the headers of the Node.js of NW.js; so are the ones built on the V8 API of Node.js, with the headers of NW.js
+  (NW.js 0.111.3 or later: the earlier releases, such as 0.72 for Windows 7, run the addons of Node-API only). On
+  Windows, the addons load the Node.js of NW.js (`node.dll`). The addons of the project are left as they are, for its
+  tests with Node.js.
 - **Bun**: Bun loads the addons of Node-API; an executable of Bun warns of the addons built on the V8 API of Node.js.
 - **Alpine (musl)**: the executables of Node.js do not load native addons there: make them with Bun.