@stacksjs/defaults 0.75.418 → 0.75.419

package/ai/skills/stacks-ui/SKILL.md

@@ -25,12 +25,13 @@ aesthetic skill. Native applications pair with `stacks-mobile` or
 - STX tags such as `<Button />` and `<Sidebar />` resolve through the plugin
   in `config/ui.ts`, `storage/framework/defaults/stx-components-plugin.ts`.
   Application `resources/components/` overrides are handled by STX. Plugin
-  roots contain the component library, framework defaults, then package roots.
+  roots contain framework defaults, the component library, then package roots.
   Installed packages contribute additive roots through `packageComponentRoots()`;
   inspect that resolver before changing precedence.
 - `STX_COMPONENTS_DIR` explicitly selects a library source directory. The
-  plugin otherwise tries a local STX development checkout and the installed
-  library. A missing component warning is a resolution problem, not proof
+  plugin otherwise uses the installed library, keeping templates with the
+  controllers the application imports. A local checkout's presence never
+  changes that selection. A missing component warning is a resolution problem, not proof
   that a tag is a globally registered Vue component.
 
 ```ts

package/ide/vscode/package.json

@@ -2,7 +2,7 @@
   "publisher": "Stacks",
   "name": "vscode-stacks",
   "displayName": "Stacks",
-  "version": "0.75.418",
+  "version": "0.75.419",
   "description": "Stacks, built into VS Code: stx templates, pickier linting and formatting, encrypted env files, the dev server preview and every buddy command. No other extensions required.",
   "license": "MIT",
   "funding": "https://github.com/sponsors/chrisbbreuer",

package/package.json

@@ -2,7 +2,7 @@
   "name": "@stacksjs/defaults",
   "type": "module",
   "sideEffects": false,
-  "version": "0.75.418",
+  "version": "0.75.419",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/stacksjs/stacks.git",
@@ -45,7 +45,7 @@
   "dependencies": {
     "@iconify-json/f7": "^1.2.2",
     "@iconify-json/hugeicons": "^1.2.35",
-    "@stacksjs/mobile": "0.75.418",
+    "@stacksjs/mobile": "0.75.419",
     "@stacksjs/sanitizer": "0.2.780",
     "@stacksjs/stx": "0.2.780",
     "@xterm/addon-fit": "^0.11.0",

package/stx-components-plugin.ts

@@ -1,5 +1,4 @@
 import { existsSync } from 'node:fs'
-import { homedir } from 'node:os'
 import { join } from 'node:path'
 
 /**
@@ -8,14 +7,12 @@ import { join } from 'node:path'
  * dashboard uses it for the macOS-style web sidebar.
  *
  * The library ships its .stx sources in the package, so the installed
- * copy is used when present. A local stx checkout wins during framework
- * development (same convention as the Craft SDK resolution in
- * `core/actions/src/dev/dashboard.ts`), and `STX_COMPONENTS_DIR` can
- * point anywhere explicitly.
+ * copy must match the package whose controllers the app imports. Merely
+ * having a development checkout on this machine must never replace those
+ * templates. `STX_COMPONENTS_DIR` selects a source directory explicitly.
  */
 const candidates = [
   process.env.STX_COMPONENTS_DIR,
-  join(homedir(), 'Code/Tools/stx/packages/components/src/ui'),
   join(process.cwd(), 'node_modules/@stacksjs/components/src/ui'),
 ].filter((dir): dir is string => Boolean(dir))