chore(deps): pin react-native-fs so Renovate dep PRs stop shipping a lockfile npm ci rejects

[dawsontoth]

Problem

Every Renovate dependency PR shipped a package-lock.json that npm ci rejected on Node 24/26, requiring a manual lockfile regeneration each time (e.g. #39's fixup, and 55c5bba before it):

npm error code EUSAGE
npm error Missing: react-native-fs@2.20.0 from lock file
npm error Missing: react-native@0.84.1 from lock file
npm error Missing: react@19.2.8 from lock file

Root cause

harper > alasql declares react-native-fs as an optionalDependency, and react-native-fs has a required peer on react-native. This trips a genuine npm install/ci divergence:

• npm install (both --package-lock-only and a full install) silently drops the entire optional react-native subtree whenever it resolves the tree from scratch — it never even attempts to place it.
• npm ci computes an ideal tree that still includes that subtree, then rejects any lock missing it. npm 11 (Node 24/26) enforces this; Node 22's older npm was lenient, which is why CI failed only on the newer matrix legs.

Renovate regenerates the lockfile from scratch when it updates dependencies — its raw output for #39 had the whole ~250-package subtree pruned (1216 entries) — so the pruned lock landed on every dep PR.

Why skipInstalls: false (c5b68bb) didn't help

That change assumed --package-lock-only was the culprit and forced a full npm install. But a full install from scratch prunes the subtree identically — the drop is in npm's ideal-tree builder, not the reify step — so #39 still shipped a pruned lock with the override already in place.

Fix

Pin react-native-fs as a direct devDependency. That makes npm treat it as required rather than optional, so npm install and npm ci resolve it identically and it survives a from-scratch regeneration. The now-redundant, disproven skipInstalls: false is removed so Renovate returns to its faster default.

• Lockfile is a clean superset: 0 added, 0 removed, 0 version changes. The large line delta is only "optional"/"peer" flags dropping off the now-required subtree.
• It's a devDependency, so the published package is unaffected. fsevents and every other platform-gated package stay optional, so Linux CI still installs cleanly.

Verification

Check	Result
npm ci on npm 11 (Node 24/26)	✅
npm ci on npm 10 (Node 22)	✅
Clean-room regen (rm lock + node_modules) + harper bump → npm ci	✅ subtree kept
Harshest full-install clean-room regen	✅ subtree kept
format:check + build + unit tests	✅

The clean-room-regen-then-npm ci test faithfully simulates a future Renovate dep PR installing on Node 24/26.

🤖 Generated with Claude Code

[gemini-code-assist]

Code Review

This pull request adds the react-native-fs dependency (version 2.20.0) to package.json and updates package-lock.json accordingly, which also removes the optional flag from numerous lockfile entries. Additionally, the skipInstalls configuration is removed from renovate.json. As there are no review comments, I have no feedback to provide.