@pylonsync/create-pylon 0.3.171 → 0.3.173

package/bin/create-pylon.js

@@ -476,7 +476,7 @@ ${platformLines.join("\n")}
 Layout:
 ${layoutLines.join("\n")}
 
-Docs: https://pylonsync.com/docs
+Docs: https://docs.pylonsync.com
 `);
 
 // ---------------------------------------------------------------------------

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pylonsync/create-pylon",
-  "version": "0.3.171",
+  "version": "0.3.173",
   "description": "Scaffold a new Pylon app — realtime backend + web/mobile/expo frontends in one command. Run via `npm create @pylonsync/pylon@latest`.",
   "publishConfig": {
     "access": "public"

package/templates/_root/README.md

@@ -40,4 +40,4 @@ bun run dev
 
 ## Docs
 
-[pylonsync.com/docs](https://pylonsync.com/docs)
+[docs.pylonsync.com](https://docs.pylonsync.com)

package/templates/vite/todo/apps/web/src/main.tsx

@@ -4,10 +4,12 @@ import { init } from "@pylonsync/react";
 import { App } from "./App";
 import "./index.css";
 
-// Same-origin baseUrl — the Vite dev server proxies /api/* to the
-// Pylon backend (see vite.config.ts). In production, configure your
-// CDN / reverse proxy the same way and this works unchanged.
-init({ baseUrl: "", appName: "__APP_NAME_SNAKE__" });
+// Omit baseUrl — Pylon defaults to window.location.origin, which the
+// Vite dev server proxies to the backend (see vite.config.ts). The
+// same setup ships to production unchanged: configure your CDN /
+// reverse proxy to forward /api/* (including the WebSocket upgrade
+// for /api/sync/ws) to your Pylon server.
+init({ appName: "__APP_NAME_SNAKE__" });
 
 const root = document.getElementById("root");
 if (!root) throw new Error("#root not found");