htmlship 0.3.0 → 0.3.1

package/README.md

@@ -18,15 +18,21 @@ npx htmlship list-mine
 
 ## Deploy built apps
 
-Build a modern frontend project (React/Vite/etc.) and publish the compiled app as one self-contained page:
+`deploy` builds a frontend project **locally** and ships the compiled output. Single-page apps (Vite, CRA, …) are inlined into one self-contained page; multi-file sites (Next.js — auto-detected — Astro, Docusaurus, …) are hosted as a file tree at `view.htmlship.com/{slug}/`.
 
 ```bash
-npx htmlship deploy ./my-app           # detect build script, build, inline, publish
-npx htmlship deploy --dry-run          # build + inline without publishing
+npx htmlship deploy ./my-app                          # SPA -> one inlined page
+npx htmlship deploy ./my-next-app                     # Next.js -> multi-file site (auto-detected)
+npx htmlship deploy ./my-app --site --out dist        # force multi-file hosting (Astro, etc.)
+npx htmlship deploy ./my-app --single-file            # force single-file inlining
+npx htmlship deploy ./my-app --password "demo-pass"   # password-protect the deploy
+npx htmlship deploy --dry-run                          # build, but don't publish
 npx htmlship deploy --build-cmd "vite build" --out dist
 ```
 
-The build runs **locally on your machine** (npm/pnpm/yarn/bun, auto-detected) — never on the server. The output is inlined into a single HTML file (≤ 10 MB) and published with relaxed sandboxing, so the app's JavaScript runs in an isolated, opaque origin (no cookies, no same-origin access, no network egress, no `eval`). The same flow is available to agents through the `deploy_project` MCP tool.
+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.
+
+For Next.js the CLI builds a static export based at the slug path automatically (no `next.config` edits) as long as the app is statically exportable — no middleware/SSR; a `next.config.ts` is the one case you configure by hand (the CLI tells you how). 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.
 
 ## MCP server
 

package/dist/cli.js

@@ -450,7 +450,7 @@ var VERSION;
 var init_version = __esm({
   "src/version.ts"() {
     "use strict";
-    VERSION = "0.3.0";
+    VERSION = "0.3.1";
   }
 });
 

package/package.json

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