feat: pass --body-limit 40MB + require jss >=0.0.208 so large app installs fit (#80)

jspod spawns jss with no --body-limit, so it rode JSS's default cap.
That blocked installing apps with a large git history through a pod —
e.g. solid-chat/app's ~30MB pack (jss install does a full clone; JSS
git-receive rejects shallow pushes), which 413'd against the old 10MB
(and even the new 20MB) default.

- Pass --body-limit 40MB when spawning jss (overridable via
  options.bodyLimit). 40MB clears the ~30MB pack with headroom without
  an over-permissive memory-DoS surface.
- Require jss >=0.0.208 <0.0.211: --body-limit only actually reaches
  Fastify from the CLI as of 0.0.208 (#562) — before that the flag was
  dead wiring — and the range floats up to 0.0.210 without re-pinning.

Bump jspod 0.0.47 → 0.0.48.

Author: melvincarvalho

lib/start.js

@@ -245,7 +245,15 @@ export async function start(userOptions = {}) {
     '--root', options.root,
     '--notifications',
     '--conneg',
-    '--mashlib-module', dataBrowserUrl
+    '--mashlib-module', dataBrowserUrl,
+    // Raise the request body limit above JSS's 20MB default so app
+    // installs with a large git history fit — e.g. solid-chat/app's
+    // ~30MB pack (`jss install` does a full clone; JSS git-receive
+    // rejects shallow pushes). 40MB clears that with headroom without
+    // an over-permissive memory-DoS surface. Needs jss >=0.0.208,
+    // where --body-limit actually reaches Fastify from the CLI (#562) —
+    // enforced by this package's dependency range.
+    '--body-limit', options.bodyLimit || '40MB'
   ];
 
   if (options.multiuser) {

package.json

@@ -1,6 +1,6 @@
 {
   "name": "jspod",
-  "version": "0.0.47",
+  "version": "0.0.48",
   "description": "JavaScript Solid Pod - Just works, batteries included",
   "type": "module",
   "main": "./lib/index.js",
@@ -60,6 +60,6 @@
   },
   "dependencies": {
     "chalk": "^5.6.2",
-    "javascript-solid-server": "^0.0.207"
+    "javascript-solid-server": ">=0.0.208 <0.0.211"
   }
 }