@floegence/floe-webapp-init 0.86.62 → 0.86.64

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@floegence/floe-webapp-init",
3
- "version": "0.86.62",
3
+ "version": "0.86.64",
4
4
  "license": "MIT",
5
5
  "type": "module",
6
6
  "description": "Scaffolding tool for Floe Webapp applications",
@@ -8,7 +8,7 @@ description: Implement, refactor, and debug Floe-Webapp apps and this monorepo u
8
8
  ## Scope
9
9
 
10
10
  - Implement or refactor repo workspace packages/apps and scaffolded Floe-Webapp apps.
11
- - Add or update registry-driven navigation (`FloeComponent`, `commands`, `statusBar`, lifecycle hooks, app-level command contributions).
11
+ - Add or update registry-driven navigation (`FloeComponent`, `commands`, lifecycle hooks, app-level command contributions).
12
12
  - Diagnose framework-usage issues and local lint/typecheck/test/build/verify failures.
13
13
 
14
14
  ## Required Inputs
@@ -37,7 +37,6 @@ rg "FloeApp|FloeRegistryRuntime|const components|FloeComponent\[]|useCommandCont
37
37
  - Stable `id` string.
38
38
  - `sidebar` metadata (`order`, `renderIn`, `fullScreen`, `hiddenOnMobile`, optional `badge`, optional `collapseBehavior`).
39
39
  - `commands` targets using the same registered ids.
40
- - `statusBar` ordering and placement when applicable.
41
40
 
42
41
  3. Validate the shell wiring still renders through the intended runtime:
43
42
 
@@ -91,7 +91,7 @@ Key fields (current core API):
91
91
  - `sidebar.fullScreen`
92
92
  - `sidebar.renderIn: 'sidebar' | 'main'`
93
93
  - `sidebar.hiddenOnMobile`
94
- - `commands`, `statusBar`
94
+ - `commands`
95
95
  - `onMount`, `onUnmount`
96
96
 
97
97
  Design note:
@@ -9,7 +9,7 @@
9
9
  "preview": "vite preview"
10
10
  },
11
11
  "dependencies": {
12
- "@floegence/floe-webapp-core": "^0.86.62",
12
+ "@floegence/floe-webapp-core": "^0.86.64",
13
13
  "solid-js": "^1.9.17"
14
14
  },
15
15
  "devDependencies": {
@@ -8,7 +8,7 @@ description: Implement, refactor, and debug Floe-Webapp apps and this monorepo u
8
8
  ## Scope
9
9
 
10
10
  - Implement or refactor repo workspace packages/apps and scaffolded Floe-Webapp apps.
11
- - Add or update registry-driven navigation (`FloeComponent`, `commands`, `statusBar`, lifecycle hooks, app-level command contributions).
11
+ - Add or update registry-driven navigation (`FloeComponent`, `commands`, lifecycle hooks, app-level command contributions).
12
12
  - Diagnose framework-usage issues and local lint/typecheck/test/build/verify failures.
13
13
 
14
14
  ## Required Inputs
@@ -37,7 +37,6 @@ rg "FloeApp|FloeRegistryRuntime|const components|FloeComponent\[]|useCommandCont
37
37
  - Stable `id` string.
38
38
  - `sidebar` metadata (`order`, `renderIn`, `fullScreen`, `hiddenOnMobile`, optional `badge`, optional `collapseBehavior`).
39
39
  - `commands` targets using the same registered ids.
40
- - `statusBar` ordering and placement when applicable.
41
40
 
42
41
  3. Validate the shell wiring still renders through the intended runtime:
43
42
 
@@ -91,7 +91,7 @@ Key fields (current core API):
91
91
  - `sidebar.fullScreen`
92
92
  - `sidebar.renderIn: 'sidebar' | 'main'`
93
93
  - `sidebar.hiddenOnMobile`
94
- - `commands`, `statusBar`
94
+ - `commands`
95
95
  - `onMount`, `onUnmount`
96
96
 
97
97
  Design note:
@@ -9,7 +9,7 @@
9
9
  "preview": "vite preview"
10
10
  },
11
11
  "dependencies": {
12
- "@floegence/floe-webapp-core": "^0.86.62",
12
+ "@floegence/floe-webapp-core": "^0.86.64",
13
13
  "solid-js": "^1.9.17"
14
14
  },
15
15
  "devDependencies": {
@@ -8,7 +8,7 @@ description: Implement, refactor, and debug Floe-Webapp apps and this monorepo u
8
8
  ## Scope
9
9
 
10
10
  - Implement or refactor repo workspace packages/apps and scaffolded Floe-Webapp apps.
11
- - Add or update registry-driven navigation (`FloeComponent`, `commands`, `statusBar`, lifecycle hooks, app-level command contributions).
11
+ - Add or update registry-driven navigation (`FloeComponent`, `commands`, lifecycle hooks, app-level command contributions).
12
12
  - Diagnose framework-usage issues and local lint/typecheck/test/build/verify failures.
13
13
 
14
14
  ## Required Inputs
@@ -37,7 +37,6 @@ rg "FloeApp|FloeRegistryRuntime|const components|FloeComponent\[]|useCommandCont
37
37
  - Stable `id` string.
38
38
  - `sidebar` metadata (`order`, `renderIn`, `fullScreen`, `hiddenOnMobile`, optional `badge`, optional `collapseBehavior`).
39
39
  - `commands` targets using the same registered ids.
40
- - `statusBar` ordering and placement when applicable.
41
40
 
42
41
  3. Validate the shell wiring still renders through the intended runtime:
43
42