fimo 0.2.3-staging.8 → 0.2.3-staging.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -36,7 +36,6 @@ pnpm add -D vite @vitejs/plugin-react @types/react @types/react-dom typescript
36
36
  "type": "module",
37
37
  "scripts": {
38
38
  "dev": "vite --host 0.0.0.0 --port 5173",
39
- "prebuild": "fimo validate",
40
39
  "build": "vite build",
41
40
  "preview": "vite preview --host 0.0.0.0 --port 4173",
42
41
  "typecheck": "tsc --noEmit"
@@ -44,6 +43,10 @@ pnpm add -D vite @vitejs/plugin-react @types/react @types/react-dom typescript
44
43
  }
45
44
  ```
46
45
 
46
+ Validate runs automatically during `fimo deploy` and API-side sandbox builds.
47
+ For a purely local build, run `fimo validate` manually first when you need to
48
+ sync schemas/forms/translations before `pnpm build`.
49
+
47
50
  ## File: `vite.config.ts`
48
51
 
49
52
  ```ts
@@ -27,7 +27,6 @@ pnpm add -D @react-router/dev @react-router/node @tailwindcss/vite tailwindcss v
27
27
  "type": "module",
28
28
  "scripts": {
29
29
  "dev": "react-router dev --port 5173",
30
- "prebuild": "fimo validate",
31
30
  "build": "react-router build && fimo export-static",
32
31
  "preview": "vite preview --host 0.0.0.0 --port 4173",
33
32
  "typecheck": "tsc --noEmit"
@@ -35,7 +34,9 @@ pnpm add -D @react-router/dev @react-router/node @tailwindcss/vite tailwindcss v
35
34
  }
36
35
  ```
37
36
 
38
- (Dependencies installed via the command above; this is the scripts shape.)
37
+ Validate runs automatically during `fimo deploy` and API-side sandbox builds.
38
+ For a purely local build, run `fimo validate` manually first when you need to
39
+ sync schemas/forms/translations before `pnpm build`.
39
40
 
40
41
  ## File: `vite.config.ts`
41
42
 
@@ -60,7 +60,7 @@ The command prints exactly which files were written, so the context-aware behavi
60
60
  You rarely have to invoke it by hand:
61
61
 
62
62
  - **Global skills auto-refresh** after a CLI version change via a marker at `~/.config/fimo/last-version`.
63
- - **The project skill auto-refreshes on `pnpm install`** when the `fimo` package version bumps — the package's postinstall hook re-syncs the skill from `node_modules/fimo/assets/skills/fimo/` (which is version-locked to the installed package). The scaffolded template approves the `fimo` and `esbuild` build scripts for pnpm (`pnpm-workspace.yaml` `allowBuilds` for pnpm 11+, plus `package.json` `pnpm.onlyBuiltDependencies` for pnpm 10-era installs). npm / yarn run lifecycle scripts by default and need no extra config.
63
+ - **The project skill auto-refreshes during Fimo-controlled installs** when the `fimo` package version bumps — the package's postinstall hook re-syncs the skill from `node_modules/fimo/assets/skills/fimo/` (which is version-locked to the installed package). For pnpm, `fimo create --install`, sandbox `fimopm install`, and E2E helper installs pass a scoped allow-all-builds flag so the hook can run without persisting build-script approvals in the template. npm / yarn run lifecycle scripts by default and need no extra config.
64
64
 
65
65
  Invoke `fimo skills sync` explicitly when iterating on skill content locally, when you bumped the package via something other than a fresh install, or any time you want to force a refresh.
66
66
 
@@ -1,5 +1,7 @@
1
1
  # Envs & branches (git-shaped workflow)
2
2
 
3
+ > **Beta:** Branch environments are still in beta. The CLI surface is available for early workflows, but not every command or cross-surface merge path is guaranteed to work reliably yet.
4
+
3
5
  A Fimo **env** is a multi-surface clone of the project: a git branch **plus** its own Neon DB branch, sandbox, preview URL, and R2 asset prefix. The CLI mirrors `git` command shapes so the workflow transfers directly — same verbs, multi-surface semantics.
4
6
 
5
7
  Every project starts with one env: `main`. You create more for feature work, deploy previews per-env, then merge back and publish.
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "bundled": true,
3
3
  "bundler": "esbuild",
4
- "bundledAt": "2026-06-23T09:32:42.732Z",
5
- "cliVersion": "0.2.3-staging.8",
4
+ "bundledAt": "2026-06-23T12:35:26.952Z",
5
+ "cliVersion": "0.2.3-staging.9",
6
6
  "external": [
7
7
  "oxc-parser",
8
8
  "fsevents"