Skip to content

Template Validation and Ecosystem Refresh

Latest
Latest

Choose a tag to compare

View all tags
@bradpotts bradpotts released this 25 Oct 05:05
v1.6.0
d8a0e3d

Contract change type: semantic change

Changed

  • Refreshed all generated templates to the current published Spectre ecosystem
    releases: shell 1.8.0, router 1.6.0, signals 1.6.1, tokens 4.15.0, UI 5.8.0,
    components 1.25.0, and the Astro adapter 4.14.0.
  • Updated Astro to 7.4.2, Vite to 8.3.5, and the CLI development toolchain.

Fixed

  • shell-app and vanilla starters now type-check out of the box:
    tsconfig.json adds vite/client types, DOM libs, noEmit, and an
    include of src and vite.config.ts, and package.json adds a
    typecheck script. Previously tsc --noEmit failed with TS2882 on the
    shell CSS side-effect import.
  • All three starters declare @phcdevworks/spectre-manifest ^2.0.0 as a
    devDependency with a check:ecosystem script, so the manifest $schema
    path resolves and the manifest validates in a fresh scaffold.
  • Renamed scaffolds no longer keep the literal spectre-app in the manifest's
    ai.safeDefaults; check:manifest-names now asserts no spectre-app
    string survives a rename.

Reported by a downstream integration using the shell-app starter.

Assets 2
Loading