@mogulmoretti/skrape 0.2.1 → 0.2.2

package/dist/cli.d.ts

@@ -1,2 +1,2 @@
 #!/usr/bin/env node
-export {};
+import './quiet.js';

package/dist/cli.js

@@ -1,4 +1,5 @@
 #!/usr/bin/env node
+import './quiet.js';
 import { createRequire } from 'node:module';
 import { join, resolve } from 'node:path';
 import { styleText } from 'node:util';

package/dist/quiet.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/quiet.js

@@ -0,0 +1,9 @@
+// Node 22 flags its built-in SQLite as experimental on first use. That notice means nothing to a
+// skrape user and would print over the UI, so drop exactly that one warning. Imported first in cli.ts.
+const emitWarning = process.emitWarning.bind(process);
+process.emitWarning = ((warning, ...rest) => {
+    if (String(warning).includes('SQLite is an experimental feature'))
+        return;
+    emitWarning(warning, ...rest);
+});
+export {};

package/dist/store/db.js

@@ -1,4 +1,5 @@
-import Database from 'better-sqlite3';
+// Node's built-in SQLite: no native module to compile, so installs never depend on a C toolchain.
+import { DatabaseSync } from 'node:sqlite';
 import { createHash } from 'node:crypto';
 import { dirname } from 'node:path';
 import { mkdirSync } from 'node:fs';
@@ -57,9 +58,9 @@ export function openDb(path) {
             mkdirSync(dir, { recursive: true });
         }
     }
-    const db = new Database(path);
-    db.pragma('journal_mode = WAL');
-    db.pragma('foreign_keys = ON');
+    const db = new DatabaseSync(path);
+    db.exec('PRAGMA journal_mode = WAL');
+    db.exec('PRAGMA foreign_keys = ON');
     db.exec(SCHEMA);
     return {
         upsertCommunity(slug, name) {

package/dist/sync.js

@@ -108,7 +108,7 @@ export async function syncClassroom(options) {
             // swallow — the caller's callback is not our concern
         }
     };
-    // A better-sqlite3 error from any of the three store calls below (disk full, locked db, FK
+    // A SQLite error from any of the three store calls below (disk full, locked db, FK
     // violation) must become a per-lesson 'failed' outcome, not a run-ending rejection: a Promise.all
     // over the worker pool would reject on the first such error while sibling workers are still in
     // flight, and the CLI's finally-block browser.close() would then race a live worker into

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mogulmoretti/skrape",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "Read Skool course content instead of watching it — pulls the classroom of a community you belong to into clean, readable transcripts.",
   "keywords": [
     "skool",
@@ -35,21 +35,19 @@
     "typecheck": "tsc --noEmit"
   },
   "engines": {
-    "node": ">=22"
+    "node": ">=22.13"
   },
   "dependencies": {
-    "better-sqlite3": "^11.5.0",
     "commander": "^12.1.0",
     "ink": "^7.1.1",
     "react": "^19.2.8",
     "zod": "^3.23.8"
   },
   "devDependencies": {
-    "@types/better-sqlite3": "^7.6.11",
     "@types/node": "^22.9.0",
     "@types/react": "^19.2.18",
     "typescript": "^5.6.3",
-    "vitest": "^2.1.4"
+    "vitest": "^3.2.7"
   },
   "optionalDependencies": {
     "playwright": "^1.48.2"