htmlship 0.3.2 → 0.3.3

package/README.md

@@ -30,7 +30,7 @@ npx htmlship deploy --dry-run                          # build, but don't publis
 npx htmlship deploy --build-cmd "vite build" --out dist
 ```
 
-The build always runs **locally on your machine** (npm/pnpm/yarn/bun, auto-detected) — never on the server. Either way the result renders in its own isolated, opaque origin (no cookies, no same-origin access, no network egress, no `eval`) via a sandboxed CSP; single-file pages and site trees are both capped at 10 MB.
+The build always runs **locally on your machine** (npm/pnpm/yarn/bun, auto-detected) — never on the server. Either way the result renders in its own isolated, opaque origin (no cookies, no same-origin access, no network egress, no `eval`) via a sandboxed CSP; single-file pages are capped at 10 MB, multi-file sites at 50 MB.
 
 For Next.js the CLI builds a static export based at the slug path automatically (no `next.config` edits — JS, `.mjs`, and `.ts` configs are all handled) as long as the app is statically exportable (no middleware/SSR). For other frameworks, `--site` ships any static build; set your framework's base path to `/__htmlship_base__` so assets resolve under `/{slug}/`. The same flow is available to agents through the `deploy_project` MCP tool.
 

package/dist/cli.js

@@ -344,7 +344,7 @@ export default typeof orig === 'function' ? ((...a) => ({ ...orig(...a), ...over
     }
   };
 }
-function packageSite(outDir, maxBytes = 10 * 1024 * 1024) {
+function packageSite(outDir, maxBytes = 50 * 1024 * 1024) {
   const files = [];
   let total = 0;
   const walk = (d) => {
@@ -456,7 +456,7 @@ var VERSION;
 var init_version = __esm({
   "src/version.ts"() {
     "use strict";
-    VERSION = "0.3.2";
+    VERSION = "0.3.3";
   }
 });
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "htmlship",
-  "version": "0.3.2",
+  "version": "0.3.3",
   "description": "Host and share HTML pages from LLMs and coding agents in one line. CLI + MCP server.",
   "keywords": [
     "html",