@tiddlywiki/mws 0.0.12 → 0.0.14

package/editions/mws-docs/tiddlers/$__StoryList.tid

@@ -1,5 +1,5 @@
-created: 20250418183134708
-list: HelloThere Installation Usage Reference
-modified: 20250418183248137
+created: 20250426194618683
+list: [[MWS and SQLite]] HelloThere Installation Usage Reference
+modified: 20250426194618683
 title: $:/StoryList
 type: text/vnd.tiddlywiki

package/editions/mws-docs/tiddlers/MWS and SQLite.md

@@ -21,3 +21,14 @@ One particular misconception to avoid is the idea that SQLite replaces the folde
 
 SQLite is perfect for MWS because it doesn't require any extra setup. But MWS is not restricted to SQLite. It uses Prisma for the database access layer, which supports several other database engines, including MariaDB (the MySQL fork) and Postgres. 
 
+# Better-SQLite3
+
+Currently WAL mode is not enabled. It has plenty of advantages, and a few minor disadvantages, but mostly it just takes extra thought to use correctly. It has more advantages for high-traffic servers that need serious concurrency. Better-SQLite3 defaults to synchronous=NORMAL for WAL mode. Eventually we will probably add a setting to enable it. 
+
+Better-SQLite3 supports multi-threading via Node workers. Either way we have to implement proper support for transactions, which mostly just means reserving a worker for the duration of the transaction. 
+
+Better-SQLite3 has foriegn keys enabled by default. 
+
+Better-SQLite3 uses native addons. If your platform isn't supported, or you need a wasm-only solution, feel free to [open an issue on Github](https://github.com/TiddlyWiki/MultiWikiServer) sharing your use-case. 
+
+MWS uses [Prisma](https://www.prisma.io) to communicate with SQLite, and in theory, MWS should work with [anything Prisma supports](https://www.prisma.io/docs/orm/overview/databases). 

package/editions/mws-docs/tiddlers/Request Server.md

@@ -0,0 +1,20 @@
+
+This is more or less a reference on the design philosophy.
+
+## HTTP request path
+
+The server comprises several classes which handle various parts of the request path. 
+
+The Listener classes call the Router class with incoming requests. The Router class starts an async (Promise-based) code path with a catch handler protecting it.
+
+There are two kinds of classes, routing and state.
+
+Routing classes hold config state for that part of the request path. They are used to reach a specific objective. Examples include the Router and Authentication classes.
+
+State classes hold information specific to each request. It may be used by any of the routing classes. The primary goal is usually to hide implementation details, or to pass information between routing classes. The StateObject class is the primary example, but modules may have their own state classes. 
+
+Both kinds of classes should check incoming information thoroughly and throw quickly if anything is wrong. The constructors of state classes are part of the request chain and may throw as well. 
+
+The request may be completed at any point in the request chain by throwing the STREAM_ENDED symbol. The catch all handler will ignore the symbol, but will send an error 500 if headers are not marked as sent at that point. 
+
+It is important that the entire request be awaited and eventually resolve or reject. A promise should never be left hanging. The Router class takes care of making sure every request has finished with some response, but if the promise never resolves or rejects, there is no way to do this. 

package/editions/mws-docs/tiddlers/Request Server.md.meta

@@ -0,0 +1,5 @@
+created: 20250422233004101
+modified: 20250422233027338
+tags: [[Architecture]]
+title: Request Server
+type: text/markdown

package/package.json

@@ -1,6 +1,7 @@
 {
   "name": "@tiddlywiki/mws",
-  "version": "0.0.12",
+  "private": false,
+  "version": "0.0.14",
   "type": "module",
   "exports": {
     "types": "./src/server.ts",
@@ -9,12 +10,14 @@
   },
   "files": [
     "dist",
-    "src",
     "prisma",
     "react-user-mgmt",
     "tiddlywiki-types",
     "editions/mws-docs",
-    "plugins/client"
+    "plugins/client",
+    "libsql",
+    "libsql-android-arm64",
+    ".env-cmdrc"
   ],
   "engines": {
     "node": ">14"
@@ -32,22 +35,26 @@
     "certs": "(cd runtime-config && bash localhost_certs.sh)",
     "start": "npm run build && node mws.dev.mjs",
     "build": "npm run tsc && tsup",
-    "install": "prisma generate",
+    "install-android": "GYP_DEFINES=\"android_ndk_path=''\" npm install",
+    "postinstall": "env-cmd -e prisma-env prisma generate",
     "env": "env",
     "test:pack": "(git clean -dfx tests && npm pack --pack-destination tests && cd tests && npm install && npm install ./tiddlywiki-mws-$npm_package_version.tgz --no-save && npm test)",
     "test": "(git clean -dfx tests && cd tests && npm install .. --no-save && npm test)",
-    "fulltest": "mv node_modules node_modules_old; npm run test:pack; mv node_modules_old node_modules"
+    "fulltest": "mv node_modules node_modules_old; npm run test:pack; mv node_modules_old node_modules",
+    "prisma:adapter:better": "cp -rfv ../prisma/packages/adapter-better-sqlite3/src/* src/adapter-better-sqlite3",
+    "prisma:adapter:libsql": "cp -rfv ../prisma/packages/adapter-libsql/src/* src/adapter-libsql"
   },
   "dependencies": {
-    "@libsql/client": "^0.8.1",
-    "@prisma/adapter-libsql": "~6.4.0",
-    "@prisma/client": "~6.4.0",
+    "@prisma/adapter-better-sqlite3": "6.7.0-dev.48",
+    "@prisma/client": "6.6.0",
     "@serenity-kit/opaque": "^0.8.4",
     "@types/mime-types": "^2.1.4",
     "@types/node": "^22.13.1",
     "@types/send": "^0.17.4",
     "@types/sjcl": "^1.0.34",
-    "prisma": "~6.4.0",
+    "@types/tiddlywiki": "file:tiddlywiki-types",
+    "env-cmd": "^10.1.0",
+    "prisma": "6.6.0",
     "source-map-support": "^0.5.21",
     "zod": "^3.24.2"
   },
@@ -64,4 +71,4 @@
   "peerDependencies": {
     "tiddlywiki": "^5.1.22"
   }
-}
+}

package/prisma/schema.prisma

@@ -7,6 +7,7 @@ generator client {
   // prisma 7 will remove the need for native node files, everything will be js and wasm
   provider        = "prisma-client-js"
   previewFeatures = ["relationJoins", "driverAdapters"]
+  binaryTargets = []
 }
 
 // generator zod {