@reventlessdev/rescript-node 2.0.0-alpha.2 → 2.0.0-alpha.4

package/CHANGELOG.md

@@ -3,6 +3,21 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# 2.0.0-alpha.4 (2026-08-11)
+
+**Note:** Version bump only for package @reventlessdev/rescript-node
+
+
+
+
+
+# 2.0.0-alpha.3 (2026-08-09)
+
+### Features
+
+* **core,aws:** bundle a runtime extension's companion packages, guard imports at deploy ([e975175](https://github.com/ReventlessDev/reventless-core/commit/e9751758f51582a8e46db362219f725bb5f1bcde))
+
+
 # 2.0.0-alpha.2 (2026-08-05)
 
 ### Features

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reventlessdev/rescript-node",
-  "version": "2.0.0-alpha.2",
+  "version": "2.0.0-alpha.4",
   "description": "ReScript bindings for the Node.js standard library",
   "license": "Apache-2.0",
   "devDependencies": {

package/src/NodeChildProcess.res

@@ -16,3 +16,32 @@ external execSync: (string, execOptions) => string = "execSync"
     string, so an argument containing shell metacharacters stays one argument. */
 @module("node:child_process")
 external execFileSync: (string, array<string>, execOptions) => string = "execFileSync"
+
+/** A running child process. Unlike the `*Sync` calls above, `spawn` returns
+    while the child is still alive, so the caller keeps working alongside it —
+    which is the whole reason to reach for this over `execFileSync`. */
+type childProcess
+
+type spawnOptions = {
+  cwd?: string,
+  /** Replaces the child's environment entirely rather than extending it. Pass
+      a copy of `NodeProcess.env` with the additions applied when the child
+      still needs PATH and friends. */
+  env?: dict<string>,
+  /** Per-descriptor disposition: `"ignore"`, `"inherit"`, or `"pipe"`, in
+      stdin/stdout/stderr order. */
+  stdio?: array<string>,
+}
+
+@module("node:child_process")
+external spawn: (string, array<string>, spawnOptions) => childProcess = "spawn"
+
+/** `null` while the child is running, its exit code once it has exited. The
+    one honest way to ask "is it still alive?" without holding an event
+    listener — a caller polling for readiness checks this to tell a slow start
+    from a process that already died. */
+@get external exitCode: childProcess => Nullable.t<int> = "exitCode"
+
+/** Signal the child. Returns whether the signal was delivered — `false` once
+    the process is already gone, which is not an error. */
+@send external kill: (childProcess, string) => bool = "kill"

package/src/NodeModule.res

@@ -10,3 +10,8 @@ type require
 external createRequire: string => require = "createRequire"
 
 @send external requireResolve: (require, string) => string = "resolve"
+
+/** The names of Node's built-in modules (both bare and some `node:`-only
+    entries like `node:test`), plus subpath forms such as `fs/promises`. */
+@module("node:module")
+external builtinModules: array<string> = "builtinModules"