@fluid-app/fluid-cli-theme-dev 0.1.522 → 0.1.523
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/dist/index.mjs +373 -54
- package/dist/index.mjs.map +1 -1
- package/dist/skills/themes-review/SKILL.md +1 -1
- package/package.json +2 -2
|
@@ -98,7 +98,7 @@ my-theme/
|
|
|
98
98
|
|
|
99
99
|
## Directory & file structure — validate first
|
|
100
100
|
|
|
101
|
-
Before reading any Liquid, walk the repo root. `fluid theme lint --json` checks schema JSON and section references,
|
|
101
|
+
Before reading any Liquid, walk the repo root. `fluid theme lint --json` checks schema JSON and section references, warns about routed page types with no template (`target.kind: "template"`), and checks `members_sites.json` the way the server does on import (`target.kind: "member_manifest"`, with the JSON path in `target.pointer`). It doesn't enforce the rest of the layout. The reviewer does.
|
|
102
102
|
|
|
103
103
|
A valid theme is recognized by the presence of an `assets/` or `config/` directory. In practice every published theme has `assets/`, `config/`, `layouts/`, and the page-type and section folders below.
|
|
104
104
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@fluid-app/fluid-cli-theme-dev",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.523",
|
|
4
4
|
"description": "Fluid CLI plugin for theme developer workflows — dev server, push, pull, init, crawl, compare",
|
|
5
5
|
"files": [
|
|
6
6
|
"dist",
|
|
@@ -21,7 +21,7 @@
|
|
|
21
21
|
"access": "public"
|
|
22
22
|
},
|
|
23
23
|
"dependencies": {
|
|
24
|
-
"@fluid-app/fluid-cli": "0.1.
|
|
24
|
+
"@fluid-app/fluid-cli": "0.1.268",
|
|
25
25
|
"chalk": "^5.6.2",
|
|
26
26
|
"chokidar": "^4.0.0",
|
|
27
27
|
"commander": "^12.0.0",
|