v1.5.10

✨ Features & docs

• @weave-framework/typescript-plugin published to npm — the .ts-side editor support. A tsserver
  plugin that synthesizes the loader-generated default export so import X from './x-component' stops
  reporting TS1192 "no default export" in WebStorm and other tsconfig-driven editors. Add
  "plugins": [{ "name": "@weave-framework/typescript-plugin" }] to your tsconfig.json compilerOptions
  and install it as a dev dependency; the Nx generator and create-weave template now scaffold both.

• Nx — use Weave in a mixed workspace (@weave-framework/nx). New guidance (and a scaffolded
  project-local tsconfig.json) for making a project use Weave tooling when it sits next to another
  framework — including migrating an Angular project. Three markers (weave.config.*, tsconfig.json,
  .prettierrc) plus a project.json target override make both the nx CLI and your editor treat the
  project — and its .html templates — as Weave rather than the framework beside it. See Adopt Weave
  one piece at a time → Make a project use Weave.

🐞 Fixes

• Tabs — tabTemplate over dynamic tabs (@weave-framework/ui). A custom tab-button template now
  renders (and refreshes) for tabs added or edited after mount, mirroring the <List> rowTemplate fix —
  the body moved into the reactive keyed tab block. (Panel content still binds at mount; a tab strip is a
  fixed set by design.)
• weave check — a @snippet satisfies a (row) => Node template prop (@weave-framework/check).
  Snippets are now typed () => Node instead of () => void, so authoring a rowTemplate / itemTemplate /
  tabTemplate as a @snippet and passing it to a locally-typed component no longer reports a spurious
  'void' is not assignable to 'Node' type error.