feat(kernel): consume published @databricks/databricks-sql-kernel napi packages (0.2.0)

Declare the eight per-platform kernel binary packages as
optionalDependencies pinned to 0.2.0, so a released @databricks/sql
pulls the matching native binding from npm on install instead of
requiring a local 'npm run build:native'. npm resolves only the package
matching the consumer's platform; the rest are skipped (optional), so
installs on unsupported platforms keep working with the Thrift backend.

Refresh native/kernel/README.md to drop the stale 'M0 / not yet
published' note now that all 8 triples are live.

Co-authored-by: Isaac
Signed-off-by: Madhavendra Rathore <madhavendra.rathore@databricks.com>

Author: msrathore-db

native/kernel/README.md

@@ -61,33 +61,36 @@ platform — each containing a single `.node` binary. `native/kernel/index.js`
 (the napi-rs router) `require()`s the package matching the consumer's
 `process.platform` / `process.arch` at load time.
 
-> **M0 status:** these per-platform packages are **not yet published**, so
-> they are intentionally **not** declared in the driver's
-> `optionalDependencies`. (npm refuses an `npm ci` against a pinned
-> dependency it cannot resolve from the registry, so declaring an
-> unpublished package would break every install.) Until they ship, the
-> binding is produced locally via `npm run build:native` (which copies
-> `index.<triple>.node` into this directory). Once the packages are
-> published, add `@databricks/databricks-sql-kernel-<triple>` back to
-> `optionalDependencies` — npm then installs only the matching one.
-
-## Supported platforms (M0)
-
-M0 targets a **single** triple: **`linux-x64-gnu`** (package
-`@databricks/databricks-sql-kernel-linux-x64-gnu`, once published).
-
-On every other platform (macOS, Windows, linux-arm64, linux-x64-musl
-/ Alpine, …) the kernel binding is simply absent: `KernelNativeLoader`
-returns `undefined` from `tryGet()` / throws a structured
-`MODULE_NOT_FOUND` hint from `get()`, and the driver continues to use
-the Thrift backend exclusively. This is expected, not a regression —
-additional triples are added to `optionalDependencies` as the kernel
-CI starts publishing them in later milestones.
+> **Status:** the per-platform packages are published on npm (kernel
+> `0.2.0`) and declared in the driver's `optionalDependencies`, pinned to
+> that exact version. `npm install` resolves only the package matching the
+> consumer's `process.platform` / `process.arch`; the others are skipped
+> (that is what `optionalDependencies` tolerates), so installing on an
+> unsupported platform does not fail. Local development can still override
+> the installed binary with `npm run build:native`, which copies a freshly
+> built `index.<triple>.node` into this directory — the router prefers that
+> local file over the installed package.
+
+## Supported platforms
+
+The driver declares all eight published triples in `optionalDependencies`:
+
+- `linux-x64-gnu`, `linux-arm64-gnu`
+- `linux-x64-musl`, `linux-arm64-musl`
+- `darwin-x64`, `darwin-arm64`
+- `win32-x64-msvc`, `win32-arm64-msvc`
+
+On any other platform (e.g. linux-arm gnueabihf, riscv64, s390x, FreeBSD)
+the kernel binding is simply absent: `KernelNativeLoader` returns
+`undefined` from `tryGet()` / throws a structured `MODULE_NOT_FOUND` hint
+from `get()`, and the driver continues to use the Thrift backend
+exclusively. This is expected, not a regression — additional triples are
+added to `optionalDependencies` as the kernel CI starts publishing them.
 
 ## Supply-chain note
 
-The unpublished triple names (`@databricks/databricks-sql-kernel-darwin-arm64`,
-`…-win32-x64-msvc`, etc.) referenced by the router are **not**
+The triple names not yet built/published (`…-linux-arm-gnueabihf`,
+`…-riscv64-gnu`, etc.) referenced by the router boilerplate are **not**
 squat-able: `@databricks` is a Databricks-owned npm scope, and npm
 only allows org members to publish under a scope it owns. A third
 party therefore cannot register `@databricks/databricks-sql-kernel-*` and have

package.json

@@ -92,6 +92,14 @@
     "winston": "^3.8.2"
   },
   "optionalDependencies": {
-    "lz4": "^0.6.5"
+    "lz4": "^0.6.5",
+    "@databricks/databricks-sql-kernel-linux-x64-gnu": "0.2.0",
+    "@databricks/databricks-sql-kernel-linux-arm64-gnu": "0.2.0",
+    "@databricks/databricks-sql-kernel-linux-x64-musl": "0.2.0",
+    "@databricks/databricks-sql-kernel-linux-arm64-musl": "0.2.0",
+    "@databricks/databricks-sql-kernel-darwin-x64": "0.2.0",
+    "@databricks/databricks-sql-kernel-darwin-arm64": "0.2.0",
+    "@databricks/databricks-sql-kernel-win32-x64-msvc": "0.2.0",
+    "@databricks/databricks-sql-kernel-win32-arm64-msvc": "0.2.0"
   }
 }