fimo 2.10.1 → 2.10.2-staging.1
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/references/assets.md +1 -23
- package/assets/skills/fimo-cli/references/content.md +1 -0
- package/assets/skills/fimo-code/references/assets.md +1 -1
- package/assets/skills/fimo-code/references/frameworks/astro.md +7 -11
- package/assets/skills/fimo-migration/references/content.md +14 -28
- package/assets/skills/fimo-migration/references/frameworks/nextjs.md +30 -42
- package/assets/skills/fimo-studio/references/cms.md +11 -37
- package/dist/cli/bundle.json +1 -1
- package/package.json +8 -8
- package/release.json +2 -2
- package/templates/astro/package.json +3 -3
- package/templates/nextjs/package.json +4 -4
- package/templates/react-router/package.json +5 -5
- package/templates/sveltekit/package.json +3 -3
- package/templates/vite/package.json +5 -5
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
# Assets workflow (media library)
|
|
2
2
|
|
|
3
3
|
> Package contract: run `fimo skills get fimo-code --ref assets` for `FimoMedia`, `--ref ui` for rendering primitives, and load the detected framework reference for framework-specific integration.
|
|
4
|
-
>
|
|
4
|
+
> To **generate** or edit images and videos with AI, and to decide when to generate, read **`references/media.md`**.
|
|
5
5
|
|
|
6
6
|
This file covers the **CLI workflow** for media that already exists: uploading files, browsing the library, inspecting reference impact, replacing references, and removing assets safely.
|
|
7
7
|
|
|
@@ -63,28 +63,6 @@ The result preserves manifest order and reports each `sourceId` as `uploaded`
|
|
|
63
63
|
or `failed`, plus final counts. Partial failure exits non-zero. Use
|
|
64
64
|
`--concurrency <1-16>` to change the default concurrency of four.
|
|
65
65
|
|
|
66
|
-
## Generate AI media
|
|
67
|
-
|
|
68
|
-
Moved to **`references/media.md`**. Choose the task that describes the outcome:
|
|
69
|
-
|
|
70
|
-
```bash
|
|
71
|
-
fimo image generate --prompt "<prompt>"
|
|
72
|
-
fimo image edit --prompt "<instruction>" --images <asset-id-or-url>
|
|
73
|
-
fimo video generate --prompt "<prompt>"
|
|
74
|
-
```
|
|
75
|
-
|
|
76
|
-
Task flags come from the API. Run `fimo <namespace> <task> --help` for the current options. Fimo owns the internal generation route.
|
|
77
|
-
|
|
78
|
-
### When to prefer generation over uploads / placeholders
|
|
79
|
-
|
|
80
|
-
- Page needs a unique hero, card thumbnail, avatar, OG image, empty-state illustration.
|
|
81
|
-
- The user describes an image / video ("a calm beach at sunset") without providing a file.
|
|
82
|
-
|
|
83
|
-
### Do NOT generate when
|
|
84
|
-
|
|
85
|
-
- The user has already uploaded or referenced a specific file.
|
|
86
|
-
- The image must be a real photo of a real thing (team photos, real product shots).
|
|
87
|
-
|
|
88
66
|
## Browse the library — `fimo assets list`
|
|
89
67
|
|
|
90
68
|
```bash
|
|
@@ -31,6 +31,7 @@ fimo singles update <Type> [--locale es] (--body '<json>' | --file <path> | --st
|
|
|
31
31
|
```
|
|
32
32
|
|
|
33
33
|
- `--body` is always a `{"data":{...}}` envelope, also for `singles update`. Put `slug` inside `data`.
|
|
34
|
+
- `entries create` and `entries update` take the body only with `--body`: they have no `--file` or `--stdin`. For a body you wrote to a file, use `bulk-create --file` or `bulk-update --file` (`--ref content/bulk`).
|
|
34
35
|
- Before you write a body, load fimo-code `content/richtext`. Rich text is Tiptap JSON (`{"type":"doc","content":[...]}`), a reference is `{"id":"<id>"}`, and media has its own shape.
|
|
35
36
|
- `get`, `update`, and `delete` take the `id` (a UUID) that `create` and `list` return. Never pass a slug as the id.
|
|
36
37
|
- `update` and `singles update` change only the top-level fields in `data`; each field you send replaces its old value. The first `singles update` for a locale creates the Single, so it needs every required field.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Assets in code
|
|
2
2
|
|
|
3
|
-
> For the CLI commands (`fimo assets upload`, `fimo image generate`,
|
|
3
|
+
> For the CLI commands, see **`fimo-cli/references/assets.md`** (`fimo assets upload`, folder management) and **`fimo-cli/references/media.md`** (`fimo image generate`, and when to generate AI images).
|
|
4
4
|
|
|
5
5
|
This file covers media fields and the Fimo image components. Image and video bytes live in the media library, never in the repository; see `SKILL.md` § Non-negotiable boundaries for the rule and its exceptions.
|
|
6
6
|
|
|
@@ -31,10 +31,9 @@ Astro site that hosts elsewhere can import `fimo` from `fimo/astro/config`
|
|
|
31
31
|
instead for the preview connector and branch env alone; the runtime
|
|
32
32
|
(`fimo/astro`, `fimo/astro/components`) always comes from `fimo`.
|
|
33
33
|
|
|
34
|
-
Compatibility:
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
existing adapter until a matching server adapter is supported.
|
|
34
|
+
Compatibility: Astro 5–7, with static output on all of them. Fimo's server
|
|
35
|
+
adapter is validated on Astro 7 only: an Astro 5/6 server app keeps its own
|
|
36
|
+
adapter.
|
|
38
37
|
|
|
39
38
|
`fimo()` loads the platform script only in Fimo previews, reports location to Studio, and performs full-page navigation when Studio changes routes. With `output: 'server'` and no adapter, it also supplies Fimo's hosted server adapter; it never replaces an adapter the application already owns for another deployment target.
|
|
40
39
|
|
|
@@ -118,13 +117,10 @@ then `<Base lang={locale} seo={seo}>`. Route templates can read
|
|
|
118
117
|
`{{article.title}}`. Apply app-owned overrides before conversion so the title,
|
|
119
118
|
Open Graph and Twitter tags agree.
|
|
120
119
|
|
|
121
|
-
The example canonical
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
follows the route's rendering and caching policy.
|
|
126
|
-
|
|
127
|
-
Full field and composition contract: read `references/frameworks/seo-head.md` when changing SEO.
|
|
120
|
+
The example canonical fits a root-hosted site: keep the app's own production
|
|
121
|
+
domain, base path and trailing-slash policy. Imported config changes need sync
|
|
122
|
+
and rebuild/redeploy. Read `references/frameworks/seo-head.md` (fields,
|
|
123
|
+
canonical and `og:url`, composition) before you change SEO.
|
|
128
124
|
|
|
129
125
|
## Static and on-demand rendering
|
|
130
126
|
|
|
@@ -8,8 +8,8 @@ Model editorial content the way an editor should see it in Fimo, and keep the
|
|
|
8
8
|
source's behavior and content shape. A better model never silently redesigns the
|
|
9
9
|
site: the same routes render the same content, in the same order, with the same
|
|
10
10
|
copy. Record the source-to-Fimo mapping - source file, frontmatter key, or
|
|
11
|
-
export column -> content type, field, block, or reference - in the
|
|
12
|
-
|
|
11
|
+
export column -> content type, field, block, or reference - in the content plan
|
|
12
|
+
(`.fimo/migration/content-plan.md`).
|
|
13
13
|
|
|
14
14
|
- **Blocks first.** Repeatable or structured editorial sections (hero, feature
|
|
15
15
|
grid, FAQ, testimonial list, pricing tiers, a page's section stack) become a
|
|
@@ -71,10 +71,9 @@ hardcoded after the worker has established that editors should manage it.
|
|
|
71
71
|
|
|
72
72
|
For each candidate:
|
|
73
73
|
|
|
74
|
-
- name it as a singular content type with a plural label (`
|
|
75
|
-
`
|
|
76
|
-
`
|
|
77
|
-
generic page route (no `EnBe`, no `Page`).
|
|
74
|
+
- name it as a singular content type with a plural label (`location`/Locations,
|
|
75
|
+
`newsPost`/News), never after a locale code or a generic page route (no
|
|
76
|
+
`EnBe`, no `Page`).
|
|
78
77
|
- infer fields from the item shape using the Field Mapping below, while keeping
|
|
79
78
|
source-specific constraints and rationale in the plain-text migration plan.
|
|
80
79
|
- push the schema, then create one entry per item.
|
|
@@ -95,27 +94,14 @@ schema merely because a shape repeats.
|
|
|
95
94
|
## Field Mapping
|
|
96
95
|
|
|
97
96
|
Choose from source semantics and the editing experience, not the source
|
|
98
|
-
container type
|
|
99
|
-
|
|
100
|
-
|
|
101
|
-
- Editor-authored prose, Markdown, HTML, or other portable formatted content ->
|
|
102
|
-
`richtext`; convert it to the current Fimo richtext contract and render it
|
|
103
|
-
with the corresponding Fimo primitive.
|
|
104
|
-
- Repeatable editor-authored structures such as FAQs, cards, features, pricing
|
|
105
|
-
items, testimonials, and page sections -> `blocks`, with nested richtext,
|
|
106
|
-
media, or references where their semantics require them.
|
|
107
|
-
- Reusable, independently editable categories, tags, authors, and similar
|
|
108
|
-
concepts -> `reference`, or blocks containing references, only when stable
|
|
109
|
-
source records or clear independent management prove the relationship.
|
|
110
|
-
- Opaque or unconstrained metadata, third-party payloads, and intentionally
|
|
111
|
-
non-editor-authored data -> generic `json`, with a concise rationale in the
|
|
112
|
-
content plan and worker report.
|
|
113
|
-
|
|
114
|
-
Then use source headers, values, and repeated patterns:
|
|
97
|
+
container type: an object or array is not by itself a reason to use `json`.
|
|
98
|
+
Use source headers, values, and repeated patterns:
|
|
115
99
|
|
|
116
100
|
- title/name/heading -> `string`
|
|
117
101
|
- slug/path/url/permalink -> `string`
|
|
118
|
-
- body/content/post/html/description -> `richtext` when editor-authored prose
|
|
102
|
+
- body/content/post/html/description -> `richtext` when editor-authored prose;
|
|
103
|
+
convert it to the current Fimo richtext contract and render it with the
|
|
104
|
+
matching Fimo primitive
|
|
119
105
|
- excerpt/summary/dek -> `text`
|
|
120
106
|
- image/photo/thumbnail/media/asset/file -> `media`, carrying the source alt on
|
|
121
107
|
the media value; never add a separate alt field (`references/media.md`)
|
|
@@ -127,9 +113,10 @@ Then use source headers, values, and repeated patterns:
|
|
|
127
113
|
- repeated section/section stack/nested item list -> `blocks` with one named
|
|
128
114
|
variant per distinct section shape
|
|
129
115
|
- category/tag/author/related item/shared entity -> `reference` to the content
|
|
130
|
-
type that models it
|
|
131
|
-
|
|
132
|
-
|
|
116
|
+
type that models it, only when stable source records or clear independent
|
|
117
|
+
management prove the relationship (see References below)
|
|
118
|
+
- opaque metadata, third-party payloads, and data no editor writes -> `json`,
|
|
119
|
+
with the reason in the content plan and the worker report
|
|
133
120
|
|
|
134
121
|
Keep media as `media`, including inside blocks, and preserve proven relationship
|
|
135
122
|
targets, direction, and cardinality. Do not turn a fixed enum, application-owned
|
|
@@ -145,7 +132,6 @@ For every content type:
|
|
|
145
132
|
- preserve slugs
|
|
146
133
|
- preserve SEO title, description, share image, canonical URL when available
|
|
147
134
|
- preserve publish status and dates
|
|
148
|
-
- preserve authors, categories, and tags as references to their content types
|
|
149
135
|
- preserve each media value's source alt text on the media value itself
|
|
150
136
|
- convert rich HTML to the current Fimo rich text representation
|
|
151
137
|
- keep source count, generated count, imported count, and skipped count in the
|
|
@@ -5,27 +5,25 @@ user explicitly chose Next.js as a conversion target. It describes what each
|
|
|
5
5
|
worker must read in that source; use the target project's `fimo-code`
|
|
6
6
|
framework guidance when implementing the migrated application.
|
|
7
7
|
|
|
8
|
-
A Next.js source stays
|
|
9
|
-
`next.config.*`, middleware, and runtime configuration
|
|
10
|
-
to
|
|
11
|
-
detection is ambiguous, stop and
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
##
|
|
15
|
-
|
|
16
|
-
When the
|
|
17
|
-
|
|
18
|
-
`
|
|
19
|
-
`fimo migrate init` actually created, keeps that single tree, and rebuilds the
|
|
8
|
+
A Next.js source stays Next.js: keep the detected router flavor,
|
|
9
|
+
`next.config.*`, middleware, and runtime configuration, and never convert the
|
|
10
|
+
app to simplify the migration. A conversion, to or from Next.js, happens only on
|
|
11
|
+
the owner's explicit choice. When framework detection is ambiguous, stop and
|
|
12
|
+
ask.
|
|
13
|
+
|
|
14
|
+
## Conversions
|
|
15
|
+
|
|
16
|
+
When the owner chose a conversion, the framework conversion worker in
|
|
17
|
+
`references/workers.md` owns the target. Into Next.js, it inspects the app tree
|
|
18
|
+
that `fimo migrate init` created, keeps that single tree, and rebuilds the
|
|
20
19
|
source routes, 404, redirects, headers, middleware, sitemap/robots/OG
|
|
21
|
-
structure, and locale routing
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
20
|
+
structure, and locale routing inside it. It ports the source's own loaders,
|
|
21
|
+
APIs, hardcoded content, and integrations unchanged; Fimo wiring comes later
|
|
22
|
+
through the content workers. The conversion passes the framework gate before
|
|
23
|
+
content data and code workers start.
|
|
25
24
|
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
claim only when its source evidence supports it.
|
|
25
|
+
Package versions suggest likely shapes, not proof: projects backport, customize,
|
|
26
|
+
and combine conventions, so accept a claim only when source evidence supports it.
|
|
29
27
|
|
|
30
28
|
## Runtime and routes
|
|
31
29
|
|
|
@@ -46,16 +44,10 @@ claim only when its source evidence supports it.
|
|
|
46
44
|
|
|
47
45
|
Load the target project's `fimo-code` `frameworks/next` and
|
|
48
46
|
`frameworks/hosting` references before implementing. Use normal Next.js
|
|
49
|
-
equivalents
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
- `not-found` and `notFound()` for framework-owned 404 behavior;
|
|
54
|
-
- metadata APIs and OG/Twitter image routes for SEO and social output;
|
|
55
|
-
- `redirects()`, `rewrites()`, `headers()`, middleware, or response headers for
|
|
56
|
-
rules that the chosen runtime actually executes; and
|
|
57
|
-
- Next.js fetch/cache/revalidation APIs only when freshness is an observable
|
|
58
|
-
requirement rather than copied provider machinery.
|
|
47
|
+
equivalents (route handlers, `notFound()`, metadata APIs and OG image routes,
|
|
48
|
+
`redirects()`/`rewrites()`/`headers()`, middleware), and cache/revalidation APIs
|
|
49
|
+
only when freshness is an observable requirement rather than copied provider
|
|
50
|
+
machinery.
|
|
59
51
|
|
|
60
52
|
These are application-level options, not guarantees that Fimo hosting supports
|
|
61
53
|
every header, redirect, route handler, cache mode, edge API, or middleware
|
|
@@ -104,11 +96,8 @@ browser.
|
|
|
104
96
|
Do not create or edit `.env` / `.env.local` for a linked project's Fimo
|
|
105
97
|
connection. Run the project's normal `next dev`, `next build`, and `next start`
|
|
106
98
|
commands, then exercise at least one server read and one client-side data read.
|
|
107
|
-
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
Keep the generated `FimoProvider` and `withFimo` integration. It supports
|
|
111
|
-
rendering Fimo Preview in Fimo Studio and enabling Edit Mode.
|
|
99
|
+
Keep the generated `FimoProvider` and `withFimo` integration: Fimo Preview in
|
|
100
|
+
Studio and Edit Mode need it.
|
|
112
101
|
|
|
113
102
|
## Locales
|
|
114
103
|
|
|
@@ -135,11 +124,10 @@ target module in `affectedFiles` before code workers start. Nested frontmatter,
|
|
|
135
124
|
mixed locale conventions, missing local assets, and unproven route references
|
|
136
125
|
need a decision from the source, not a guess.
|
|
137
126
|
|
|
138
|
-
Map what the source proves
|
|
139
|
-
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
than using a filename or extension as an automatic classification.
|
|
127
|
+
Map what the source proves, from the consuming route and data shape, never from a
|
|
128
|
+
filename or extension alone: a directory of Markdown files may be one
|
|
129
|
+
collection, locale-suffixed files may be locale payloads of one document, and a
|
|
130
|
+
`public/` reference may become a media upload.
|
|
143
131
|
|
|
144
132
|
Preserve how that content reaches the page. Local Markdown rendered during a
|
|
145
133
|
Next build stays a Server Component or static-generation read after it moves to
|
|
@@ -162,9 +150,9 @@ observable order explicitly. The matching data batch count must equal the
|
|
|
162
150
|
source item count. A schema and query with zero planned entry items is an
|
|
163
151
|
incomplete handoff.
|
|
164
152
|
|
|
165
|
-
|
|
166
|
-
|
|
167
|
-
|
|
153
|
+
A read-only extractor follows `workers/content-planner` (Optional extraction
|
|
154
|
+
helpers); a general Next.js AST parser is not required. Record the mapping in
|
|
155
|
+
the content plan and the worker report.
|
|
168
156
|
|
|
169
157
|
Content that is not file-backed follows the content planner's discovery branches
|
|
170
158
|
in `references/workers.md`; preserve every provider gap as unresolved evidence.
|
|
@@ -1,27 +1,20 @@
|
|
|
1
1
|
## How the CMS Works
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Content (the database icon) holds the site's structured content:
|
|
4
4
|
|
|
5
|
-
- **Pages**
|
|
6
|
-
- **Collections** hold
|
|
7
|
-
- **Singles** hold one set of content, such as Site settings
|
|
8
|
-
- **
|
|
9
|
-
|
|
10
|
-
Both use schemas to define their fields. The difference is whether you edit one set of content or manage a repeatable list.
|
|
5
|
+
- **Pages** group the Labels, Singles, and Collection queries each route declares.
|
|
6
|
+
- **Collections** hold many entries of one kind, such as Blog posts or Testimonials. Open one to search, sort, create, and manage its entries.
|
|
7
|
+
- **Singles** hold one set of content, such as Site settings or a Homepage. Open one and edit it directly.
|
|
8
|
+
- **Forms** lists the submissions collected by the site's forms: open and delete them, or export them as CSV.
|
|
9
|
+
- **Labels & Text** is where you edit the site's interface copy as key-and-value rows, not translated copies of entries.
|
|
11
10
|
|
|
12
11
|
Pages is still a pre-release Studio surface. It is visible in development and staging, but hidden in production until the public release. If Pages is absent, use Collections, Singles, and Labels & Text normally.
|
|
13
12
|
|
|
14
13
|
## Browsing Your Content
|
|
15
14
|
|
|
16
|
-
1. Open **Content**
|
|
17
|
-
2.
|
|
18
|
-
3.
|
|
19
|
-
4. Pages shows the site's route tree. Collections and Singles show cards for the schemas in that group.
|
|
20
|
-
5. Select a page to edit its declared sources together. For a dynamic route, choose the concrete entry from the header selector.
|
|
21
|
-
6. Click a Collection to see its entries, then click an entry to edit it.
|
|
22
|
-
7. Click a Single to edit it directly.
|
|
23
|
-
|
|
24
|
-
Collection cards show their entry count. Single cards are labeled **Single** instead because they always represent one set of content.
|
|
15
|
+
1. Open **Content** and choose **Pages**, **Collections**, **Singles**, **Forms**, or **Labels & Text** in the left sidebar. Hover over or focus the info icon beside any item for a short explanation.
|
|
16
|
+
2. Pages shows the site's route tree. Select a page to edit its declared sources together; for a dynamic route, choose the concrete entry from the header selector.
|
|
17
|
+
3. Collections and Singles show cards for their schemas. Collection cards show their entry count; Single cards are labeled **Single**.
|
|
25
18
|
|
|
26
19
|
## Editing by Page
|
|
27
20
|
|
|
@@ -38,11 +31,7 @@ A route with several parameters, such as `/shop/:category/:product`, is chosen l
|
|
|
38
31
|
|
|
39
32
|
## Editing a Single
|
|
40
33
|
|
|
41
|
-
|
|
42
|
-
2. Select the Single you want, such as Site settings.
|
|
43
|
-
3. Update its fields.
|
|
44
|
-
|
|
45
|
-
Changes save automatically. A Single has no entry list, create action, bulk actions, or delete action because it always represents the same set of content.
|
|
34
|
+
Open **Content → Singles**, select the Single (such as Site settings), and update its fields. Changes save automatically. A Single has no entry list, create action, bulk actions, or delete action.
|
|
46
35
|
|
|
47
36
|
## Navigating the Entry List
|
|
48
37
|
|
|
@@ -110,19 +99,4 @@ Bulk operations are available for Collections, not Singles.
|
|
|
110
99
|
|
|
111
100
|
## Working with AI
|
|
112
101
|
|
|
113
|
-
The AI chat can
|
|
114
|
-
|
|
115
|
-
- Ask the AI to **create a Single or Collection** (for example, "Create a Site settings Single" or "Create a Testimonials Collection with name, quote, and photo fields").
|
|
116
|
-
- Ask it to **populate entries** (for example, "Add 5 sample blog posts about web design").
|
|
117
|
-
- Use **@** in the chat to reference specific content when discussing changes.
|
|
118
|
-
- Ask the AI to **wire content to a page** so entries display on your site automatically.
|
|
119
|
-
|
|
120
|
-
## Key Concepts
|
|
121
|
-
|
|
122
|
-
- **Collections** are best for repeatable content. Open one to search, sort, create, and manage its entries.
|
|
123
|
-
- **Singles** are best for one-off content. Open one and edit it directly.
|
|
124
|
-
- **Pages** organize existing labels and entries around the structure of the site.
|
|
125
|
-
- **Page sources organize usage, not entry membership.** A Collection query decides which reusable entries the Pages workspace shows; the entries remain available under Collections.
|
|
126
|
-
- **Forms tab**: View and manage form submissions collected from your site's forms.
|
|
127
|
-
- **Labels & Text tab**: Edit your site's UI labels and static text strings as key-and-value rows. This is for your site's interface copy, not for translated copies of collection entries.
|
|
128
|
-
- **Search and sort**: Use the search bar to filter entries and the sort dropdown to order them quickly.
|
|
102
|
+
The AI chat can create a Single or Collection ("Create a Testimonials Collection with name, quote, and photo fields"), add entries ("Add 5 sample blog posts about web design"), and wire content to a page so entries display on the site. Use **@** in the chat to reference specific content.
|
package/dist/cli/bundle.json
CHANGED
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "fimo",
|
|
3
|
-
"version": "2.10.1",
|
|
3
|
+
"version": "2.10.2-staging.1",
|
|
4
4
|
"description": "Fimo CLI - create, deploy, and manage Fimo sites",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"astro-component"
|
|
@@ -194,13 +194,13 @@
|
|
|
194
194
|
"devDependencies": {
|
|
195
195
|
"@clack/core": "^1.2.0",
|
|
196
196
|
"@clack/prompts": "^1.2.0",
|
|
197
|
-
"@fimo/agents-bundle": "2.10.1",
|
|
198
|
-
"@fimo/api-contracts": "2.10.1",
|
|
199
|
-
"@fimo/cli-kit": "2.10.1",
|
|
200
|
-
"@fimo/framework-detect": "2.10.1",
|
|
201
|
-
"@fimo/routes": "2.10.1",
|
|
202
|
-
"@fimo/sdk": "2.10.1",
|
|
203
|
-
"@fimo/tsconfig": "2.10.1",
|
|
197
|
+
"@fimo/agents-bundle": "2.10.2-staging.1",
|
|
198
|
+
"@fimo/api-contracts": "2.10.2-staging.1",
|
|
199
|
+
"@fimo/cli-kit": "2.10.2-staging.1",
|
|
200
|
+
"@fimo/framework-detect": "2.10.2-staging.1",
|
|
201
|
+
"@fimo/routes": "2.10.2-staging.1",
|
|
202
|
+
"@fimo/sdk": "2.10.2-staging.1",
|
|
203
|
+
"@fimo/tsconfig": "2.10.2-staging.1",
|
|
204
204
|
"@types/node": "22.18.6",
|
|
205
205
|
"agent-install": "^0.0.5",
|
|
206
206
|
"astro": "^7.1.6",
|
package/release.json
CHANGED
|
@@ -9,9 +9,9 @@
|
|
|
9
9
|
"check": "astro sync && astro check"
|
|
10
10
|
},
|
|
11
11
|
"dependencies": {
|
|
12
|
-
"fimo": "2.10.1",
|
|
13
|
-
"fimo-analytics": "2.10.1",
|
|
14
|
-
"fimo-astro": "2.10.1",
|
|
12
|
+
"fimo": "2.10.2-staging.1",
|
|
13
|
+
"fimo-analytics": "2.10.2-staging.1",
|
|
14
|
+
"fimo-astro": "2.10.2-staging.1",
|
|
15
15
|
"zod": "^4.4.3"
|
|
16
16
|
},
|
|
17
17
|
"devDependencies": {
|
|
@@ -12,10 +12,10 @@
|
|
|
12
12
|
},
|
|
13
13
|
"dependencies": {
|
|
14
14
|
"@tanstack/react-query": "^5.80.6",
|
|
15
|
-
"fimo": "2.10.1",
|
|
16
|
-
"fimo-analytics": "2.10.1",
|
|
17
|
-
"fimo-next": "2.10.1",
|
|
18
|
-
"fimo-react": "2.10.1",
|
|
15
|
+
"fimo": "2.10.2-staging.1",
|
|
16
|
+
"fimo-analytics": "2.10.2-staging.1",
|
|
17
|
+
"fimo-next": "2.10.2-staging.1",
|
|
18
|
+
"fimo-react": "2.10.2-staging.1",
|
|
19
19
|
"next": "16.4.2",
|
|
20
20
|
"react": "^19.2.7",
|
|
21
21
|
"react-dom": "^19.2.7",
|
|
@@ -21,11 +21,11 @@
|
|
|
21
21
|
"cn": "0.2.4",
|
|
22
22
|
"date-fns": "^4.1.0",
|
|
23
23
|
"embla-carousel-react": "^8.6.0",
|
|
24
|
-
"fimo": "2.10.1",
|
|
25
|
-
"fimo-analytics": "2.10.1",
|
|
26
|
-
"fimo-react": "2.10.1",
|
|
27
|
-
"fimo-react-router": "2.10.1",
|
|
28
|
-
"fimo-vite": "2.10.1",
|
|
24
|
+
"fimo": "2.10.2-staging.1",
|
|
25
|
+
"fimo-analytics": "2.10.2-staging.1",
|
|
26
|
+
"fimo-react": "2.10.2-staging.1",
|
|
27
|
+
"fimo-react-router": "2.10.2-staging.1",
|
|
28
|
+
"fimo-vite": "2.10.2-staging.1",
|
|
29
29
|
"input-otp": "^1.4.2",
|
|
30
30
|
"isbot": "^5",
|
|
31
31
|
"lucide-react": "^0.577.0",
|
|
@@ -11,9 +11,9 @@
|
|
|
11
11
|
"prepare": "svelte-kit sync"
|
|
12
12
|
},
|
|
13
13
|
"dependencies": {
|
|
14
|
-
"fimo": "2.10.1",
|
|
15
|
-
"fimo-analytics": "2.10.1",
|
|
16
|
-
"fimo-sveltekit": "2.10.1",
|
|
14
|
+
"fimo": "2.10.2-staging.1",
|
|
15
|
+
"fimo-analytics": "2.10.2-staging.1",
|
|
16
|
+
"fimo-sveltekit": "2.10.2-staging.1",
|
|
17
17
|
"zod": "^4.4.3"
|
|
18
18
|
},
|
|
19
19
|
"devDependencies": {
|
|
@@ -11,11 +11,11 @@
|
|
|
11
11
|
},
|
|
12
12
|
"dependencies": {
|
|
13
13
|
"@tanstack/react-query": "^5.80.6",
|
|
14
|
-
"fimo": "2.10.1",
|
|
15
|
-
"fimo-analytics": "2.10.1",
|
|
16
|
-
"fimo-react": "2.10.1",
|
|
17
|
-
"fimo-react-router": "2.10.1",
|
|
18
|
-
"fimo-vite": "2.10.1",
|
|
14
|
+
"fimo": "2.10.2-staging.1",
|
|
15
|
+
"fimo-analytics": "2.10.2-staging.1",
|
|
16
|
+
"fimo-react": "2.10.2-staging.1",
|
|
17
|
+
"fimo-react-router": "2.10.2-staging.1",
|
|
18
|
+
"fimo-vite": "2.10.2-staging.1",
|
|
19
19
|
"react": "^19.2.7",
|
|
20
20
|
"react-dom": "^19.2.7",
|
|
21
21
|
"react-router": "^8.3.0",
|