@homepages/template-cli 0.1.0 → 0.1.1

package/CHANGELOG.md

@@ -0,0 +1,69 @@
+# @homepages/template-cli
+
+## 0.1.1
+
+### Patch Changes
+
+- 10f53a7: `template-kit dev`'s canvas hover/select ring no longer overflows the page's
+  x-axis when hovering a full-bleed section (e.g. a hero or header flush with
+  both page edges). The ring's geometry inflated the target's bounding rect by
+  a fixed offset on every side with no bound, so a rect already touching the
+  document edge pushed the ring 2px past it, growing the iframe's horizontal
+  scroll extent. The ring box is now clamped to `[0, containerWidth]`.
+- f3f6d70: `template-kit check` no longer fails on a tsconfig `paths` alias (e.g.
+  `"@/platform/*": ["../platform/*"]`) or on a section whose contract files
+  share a module large enough for esbuild to code-split. Previously the
+  loader's css-stub plugin decided "external vs. bundle" from the specifier's
+  own text, so a `paths`-resolved alias got re-emitted as a literal bare
+  import Node couldn't resolve; separately, the loader's build applied
+  `publicPath` to code-split `chunk-*.js` cross-imports the same way it does
+  to real asset files, producing an import path Node couldn't resolve either.
+  Both are now decided from the actual resolved file, and `publicPath` is no
+  longer set on the loader's build.
+- 1c2c2db: `template-kit dev`'s preview server no longer 500s on `/runtime/base.css`.
+  The route resolved the file at a path the build never emits to
+  (`dist/css/base.css`; the build copies it flat to `dist/base.css`), so every
+  section rendered unstyled — Tailwind-derived colors and layout were silently
+  missing everywhere, only arbitrary-value element geometry survived. The route
+  now resolves the stylesheet through `@homepages/template-kit`'s own
+  `./base.css` export, so the kit's internal layout is no longer something this
+  package can guess wrong about.
+- 989d23e: `template-kit dev` gains an optional `--diagnostics-cmd` flag: point it at any
+  command that prints `{"violations": [...]}` JSON for a `--template`/`--section`
+  pair, and the standalone section preview
+  (`/sections/<template>/<section>/<fixture>`) shows a dismissible banner when it
+  reports violations. Unset by default — no behavior change for a workspace that
+  doesn't configure it.
+- e1d5792: `template-kit dev`'s preview server now compiles a template's theme-color
+  Tailwind utilities (`bg-primary`, `text-ink`, `bg-background`, etc.) instead
+  of silently dropping them. `assembleTemplateCss` used to concatenate the
+  compiled theme (`compileThemeToCss`, the `@theme inline` alias layer plus
+  its `:root` custom props) onto Tailwind's CLI output _after_ the CLI had
+  already run, so the theme's color tokens were never part of the build graph
+  Tailwind scanned — `@theme` outside that graph is inert, and silently so, so
+  any utility built on a template color never got generated. No error, no
+  warning: every section rendered with correct layout but default
+  black-on-white text and backgrounds. The theme partial is now written to the
+  dev cache and `@import`ed into the Tailwind entry ahead of the section
+  `@source` scans, mirroring how the registry's own publish pipeline
+  (`ci/build-css.ts`) has always assembled it. `fontFaces` is still prepended
+  to the final bundle separately, since a nested `@import url(...)` doesn't
+  hoist out of an imported partial.
+- 2e36277: Escape `>` and `&` as well as `<` in the dev server's island map, matching the escaping used by published pages.
+- ff1d6de: `template-kit dev`'s canvas mirror now shows the Islands inspector panel for a
+  section-level selection, not just a slot selection. A `fill-parent`/`fill-self`
+  island with no owning slot of its own only ever gets its shield dropped by a
+  section-level click, so the panel previously could show it as `shielded` but
+  never `interactive`. Existing slot-selection behavior (edit panel + Islands
+  list) is unchanged.
+- 41d0e88: `template-kit dev` now honors a workspace's tsconfig `paths` when resolving
+  imports, the same way `check` already does via esbuild's native tsconfig
+  lookup. Previously the dev server's Vite instance had no `paths` awareness at
+  all, so a workspace mapping (e.g. `"@/lib/*": ["../lib/*"]`) that made `check`
+  pass left `dev` 500ing with `Cannot find module`. A workspace with no `paths`
+  mapping is unaffected.
+- Updated dependencies [5030122]
+- Updated dependencies [f868a43]
+- Updated dependencies [b7bfc96]
+- Updated dependencies [1c4c7dd]
+  - @homepages/template-kit@0.9.0

package/dist/package.js

@@ -1,5 +1,5 @@
 //#region package.json
-var version = "0.1.0";
+var version = "0.1.1";
 
 //#endregion
 export { version };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@homepages/template-cli",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "description": "The template-kit CLI: check, dev (with the canvas playground), new, pack, theme, and link. Peers @homepages/template-kit.",
   "license": "UNLICENSED",
   "type": "module",