Summary
@effect/sql-sqlite-node currently depends on better-sqlite3@^12.6.2. The v12 line of better-sqlite3 installs its prebuilt binding through prebuild-install, which is no longer maintained, so every fresh install of anything depending on @effect/sql-sqlite-node now prints:
npm warn deprecated prebuild-install@7.1.3: No longer maintained. Please contact the author of the relevant native addon; alternatives are available.
better-sqlite3 v13 dropped prebuild-install entirely — 13.0.3's dependencies are just node-addon-api — so bumping the range to ^13 removes the deprecated transitive dependency and silences the warning for downstream consumers.
Ask
Bump better-sqlite3 from ^12.6.2 to ^13 in @effect/sql-sqlite-node (with whatever Node floor / API review the major bump warrants on your side).
Happy to open the PR if that's welcome.
Context
Hit while shipping a CLI (npx @eto-press/cli) whose journal runs on @effect/sql-sqlite-node — the deprecation warning is the first thing a new user sees on a cold install, several layers above their control. overrides can't help downstream here, since npx consumers install the package as a dependency, not a root.
Summary
@effect/sql-sqlite-nodecurrently depends onbetter-sqlite3@^12.6.2. The v12 line of better-sqlite3 installs its prebuilt binding throughprebuild-install, which is no longer maintained, so every fresh install of anything depending on@effect/sql-sqlite-nodenow prints:better-sqlite3 v13 dropped
prebuild-installentirely —13.0.3's dependencies are justnode-addon-api— so bumping the range to^13removes the deprecated transitive dependency and silences the warning for downstream consumers.Ask
Bump
better-sqlite3from^12.6.2to^13in@effect/sql-sqlite-node(with whatever Node floor / API review the major bump warrants on your side).Happy to open the PR if that's welcome.
Context
Hit while shipping a CLI (
npx @eto-press/cli) whose journal runs on@effect/sql-sqlite-node— the deprecation warning is the first thing a new user sees on a cold install, several layers above their control.overridescan't help downstream here, since npx consumers install the package as a dependency, not a root.