fimo 0.15.0 → 0.16.0-staging.2

package/dist/runtime/sveltekit/runtime.js

@@ -1,6 +1,9 @@
+import { env as publicEnv } from '$env/dynamic/public';
 import { requireContentApiUrl } from '../content/client/runtime.js';
 function resolveApiUrl(apiUrl) {
-    return apiUrl ?? (typeof process === 'undefined' ? undefined : process.env.PUBLIC_FIMO_API_URL);
+    return (apiUrl ??
+        publicEnv.PUBLIC_FIMO_API_URL ??
+        (typeof process === 'undefined' ? undefined : process.env.PUBLIC_FIMO_API_URL));
 }
 export function createSvelteKitContentRuntime(options) {
     const apiUrl = resolveApiUrl(options.apiUrl);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fimo",
-  "version": "0.15.0",
+  "version": "0.16.0-staging.2",
   "description": "Fimo CLI - create, deploy, and manage Fimo projects",
   "bin": {
     "fimo": "dist/cli/index.js"

package/release.json

@@ -1,5 +1,5 @@
 {
   "source": "npm",
-  "apiUrl": "https://api.fimo.ai",
-  "webUrl": "https://fimo.ai"
+  "apiUrl": "https://api.staging.fimo.team",
+  "webUrl": "https://staging.fimo.team"
 }

package/templates/astro/AGENTS.md

@@ -31,6 +31,7 @@ a code-only task, or use `npx fimo@latest` for project-local code generation and
 - Use generated schema clients, `getLabels({ locale })`, and native components from `fimo/astro/components` for editable values.
 - Do not add React or a second deployment platform.
 - Never edit `.fimo/project.json`; it links this directory to the remote project.
+- Keep `.fimo/config.json#runtime` true to the code: framework, `dev`/`build`/`install` commands, output directory. Update it when you rename a package script, move the build output, or change framework; the reference is `fimo skills get fimo-code --ref frameworks/hosting`.
 - Keep secrets in the Fimo dashboard, not committed environment files.
 - Pass flags to interactive Fimo commands when scripting them.
 

package/templates/nextjs/AGENTS.md

@@ -38,6 +38,7 @@ The scaffolded homepage is disposable. Replace it on the first real generation.
 - The application owns routes, locale resolution, links, HTML language/direction, and SEO. Fimo connects to those decisions.
 - Do not add a second deployment platform.
 - Never edit `.fimo/project.json`; it links this directory to the remote project.
+- Keep `.fimo/config.json#runtime` true to the code: framework, `dev`/`build`/`install` commands, output directory. Update it when you rename a package script, move the build output, or change framework; the reference is `fimo skills get fimo-code --ref frameworks/hosting`.
 - Keep secrets in the Fimo dashboard, not in committed environment files.
 - Pass flags to interactive Fimo commands when scripting them.
 

package/templates/react-router/AGENTS.md

@@ -42,6 +42,7 @@ breaks that. Load `fimo-code` for the exact primitives, but the rule is:
 - **Deploy is on-demand**, not a save step. Batch related edits into one deploy.
 - Do not add a second deploy tool (Vercel, Netlify, etc.).
 - **Never edit `.fimo/project.json`** — it links this folder to the remote project.
+- **Keep `.fimo/config.json#runtime` true to the code** — framework, `dev`/`build`/`install` commands, output directory. Update it when you rename a package script, move the build output, or change framework; the reference is `fimo skills get fimo-code --ref frameworks/hosting`.
 - The scaffolded homepage is disposable starter content. Replace it on the first real generation.
 - **Secrets live in the Fimo dashboard**, not in a committed `.env`.
 - When scripting, pass flags to `fimo` commands (`fimo deploy -m "…"`, `fimo delete -y`) — bare interactive forms hang in non-TTY shells.

package/templates/react-router/package.json

@@ -21,7 +21,7 @@
     "cmdk": "^1.1.1",
     "date-fns": "^4.1.0",
     "embla-carousel-react": "^8.6.0",
-    "fimo": "0.15.0",
+    "fimo": "0.16.0-staging.2",
     "input-otp": "^1.4.2",
     "isbot": "^5",
     "lucide-react": "^0.577.0",

package/templates/sveltekit/AGENTS.md

@@ -30,6 +30,7 @@ a code-only task, or use `npx fimo@latest` for project-local code generation and
 - The application owns routes, locale resolution, links, HTML language/direction, and SEO. Fimo connects to those decisions.
 - Do not add a second deployment platform.
 - Never edit `.fimo/project.json`; it links this directory to the remote project.
+- Keep `.fimo/config.json#runtime` true to the code: framework, `dev`/`build`/`install` commands, output directory. Update it when you rename a package script, move the build output, or change framework; the reference is `fimo skills get fimo-code --ref frameworks/hosting`.
 - Keep secrets in the Fimo dashboard, not committed environment files.
 - Pass flags to interactive Fimo commands when scripting them.