fimo 1.1.0-staging.1 → 1.1.0-staging.2
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-code/references/frameworks/compatibility.md +6 -0
- package/dist/cli/bundle.json +1 -1
- package/dist/cli/index.js +5 -5
- package/dist/scripts/sync-schemas.js +17 -3
- package/package.json +7 -7
- package/templates/astro/package.json +2 -2
- package/templates/nextjs/package.json +3 -3
- package/templates/react-router/package.json +4 -4
- package/templates/sveltekit/package.json +2 -2
- package/templates/vite/package.json +4 -4
|
@@ -23,6 +23,12 @@ Vite plugin from `fimo-react-router/vite`, which builds on the installed
|
|
|
23
23
|
SvelteKit installs `fimo` and `fimo-sveltekit`. Move a project to a new release
|
|
24
24
|
with `fimo update <exact-version>`, which keeps the whole set on one version.
|
|
25
25
|
|
|
26
|
+
React projects pinned before framework companions shipped keep their legacy
|
|
27
|
+
runtime imports. The current CLI generates content clients through `fimo/ui`
|
|
28
|
+
for those projects and does not require `fimo-react`. Run `fimo update
|
|
29
|
+
<exact-version>` only when the developer chooses to move the project to a split
|
|
30
|
+
runtime release.
|
|
31
|
+
|
|
26
32
|
`runtime.framework` must match a dependency in `package.json`; a profile the
|
|
27
33
|
code does not use fails the production build. Shape and rules: `hosting.md`
|
|
28
34
|
§ `runtime`.
|