fimo 0.16.0-staging.1 → 0.16.0-staging.3
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.
- package/assets/skills/fimo-cli/SKILL.md +2 -0
- package/dist/cli/bundle.json +1 -1
- package/dist/cli/index.js +2 -2
- package/dist/runtime/sveltekit/runtime.js +4 -1
- package/package.json +1 -1
- package/templates/astro/package.json +1 -1
- package/templates/nextjs/package.json +1 -1
- package/templates/react-router/package.json +2 -2
- package/templates/react-router/pnpm-workspace.yaml +1 -1
- package/templates/sveltekit/package.json +1 -1
|
@@ -68,6 +68,8 @@ The working loop is local: run the app with the project's package-manager `dev`
|
|
|
68
68
|
|
|
69
69
|
`fimo validate` is the single entrypoint for "prove this project is ready" — it covers schema/form codegen, route metadata checks, lint, and missing label checks for `i18n.defaultLocale` from `.fimo/config.json` (fallback: `en`). Use `fimo labels set` / `set-many` to create or update label values in the DB. The underlying phases are also available individually under the hidden `fimo scripts` namespace for advanced/debug use.
|
|
70
70
|
|
|
71
|
+
Keep `fimo validate --json` at the front of the project's `build` script, which is where the bundled templates put it. The hosted build runs that script, so validation runs on the exact code being published and a rejected build reports the failing rule instead of a generic build error. Removing it is the developer's call, but do not drop it while editing `package.json` for other reasons.
|
|
72
|
+
|
|
71
73
|
## Decision Tree
|
|
72
74
|
|
|
73
75
|
Load the matching reference when the user's request fires its trigger. Recipes that involve writing code also need the `fimo-code` skill's package references — they're called out where relevant.
|