fix: quote argument-hint YAML values so Copilot CLI ≥1.0.65 loads all skills
`argument-hint: [foo]` YAML-parses as a flow sequence (array), not a
string. Downstream slash-command loaders that validate `argument-hint`
as a string — notably GitHub Copilot CLI ≥ 1.0.65 — silently reject
the skill on load, and the command disappears from the CLI menu.
Wrap the value in double quotes so it parses as a string. No behaviour
change on Claude Code.
* fix(docs): replace dead chakra-ui.com/discord link with discord.gg invite
The blog posts all link to https://chakra-ui.com/discord, which returns
HTTP 404. The marketing site has retired the /discord path; the current
Discord invite is https://discord.gg/chakra-ui (verified on the live
homepage footer). Replaced in 10 blog posts published between August
2025 and March 2026.
* Delete .changeset/fix-blog-discord-link.md
---------
Co-authored-by: sanjibani <18418553+sanjibani@users.noreply.github.com>
Co-authored-by: Segun Adebayo <joseshegs@gmail.com>
* fix(docs): replace Stack.Separator with standalone Separator in migration guide
The StackDivider section in the v2-to-v3 migration guide told users
to migrate to `Stack.Separator`, which is not a valid export from
`@chakra-ui/react` - `Stack` is not a compound/namespaced component
in v3 and never exposed `Separator` as a property. Users following
the guide encountered runtime `Cannot read properties of undefined`
errors and TS `Property 'Separator' does not exist on type 'Stack'`.
Replaced both references (StackDivider section and Stack Props example)
with the standalone `Separator` component documented at
https://chakra-ui.com/docs/components/separator. Added the import
statement in the StackDivider example to match the Separator docs
style; the Stack Props example keeps the inline-style so the diff
stays scoped to the property rename.
Closes#10881
* chore: add changeset for Stack.Separator docs fix
---------
Co-authored-by: sanjibani <18418553+sanjibani@users.noreply.github.com>
Recipe components (Button, Badge, Skeleton, etc.) previously recompiled
their recipe and re-resolved variant styles per instance/render, which
dominated render time in large lists and tables.
- Cache compiled recipes per system instance, keyed by recipe key
- Memoize cva/sva variant resolution so results are referentially stable
- Drop the per-instance structuredClone of recipe configs
- Fix recipe merging so it no longer throws or mutates source configs
- Use tsgo (@typescript/native-preview) for faster typecheck
* Rename TanStackRouterVite to tanstackRouter
The exported function `TanStackRouterVite` is marked as deprecated in latest documentation.
As suggested in the documentations, `tanstackRouter` must be used instead.
* Update vite.config.ts
Node 22+ provides a global fetch, so node-fetch is no longer needed.
HTTPS_PROXY support moves from https-proxy-agent (the `agent` option) to
undici's ProxyAgent via the standard `dispatcher` option, centralized in
a small request() helper. Also drops the now-unused node-fetch dependency
from apps/www, removing the deprecated transitive node-domexception.
Resolves discussion #10039.
find-up v8 pulls unicorn-magic@0.3.0, whose package.json uses bare
condition keys in "exports" with no main entry. tsx's module resolver
rejects this (ERR_PACKAGE_PATH_NOT_EXPORTED), breaking the docs
prebuild (scripts/composition.ts etc.) and the Vercel docs deploy.
We only ever use findUpSync(name, { type }). Switch to find-up-simple
(same author, zero dependencies, identical findUpSync API, clean
exports) instead of pinning find-up back to v7. Updates the 5 import
sites in scripts/ and apps/www.
Verified: full docs build, root typecheck, and prettier all pass.
Applies the non-major bumps from Renovate PR #10525 onto current main,
skipping entries main has already advanced past (@ark-ui/react is
already 5.37.2 > the PR's 5.37.1; @internationalized/date and the pnpm
packageManager pin are also ahead).
Notable: storybook 10.3.3 -> 10.4.2, vite 8.0.2 -> 8.0.16, vitest
4.1.1 -> 4.1.8, rollup 4.57.1 -> 4.61.1, esbuild ^0.27.3 -> ^0.28.0,
next 15.5.18 -> 15.5.19, prettier 3.8.1 -> 3.8.3, plus assorted
patch/minor deps across packages, apps, and sandboxes.
Verified green: typecheck, lint, format:check, build, and the full
vitest suite (978 tests).
Batches three Renovate dependency updates:
- find-up 7.0.0 -> 8.0.0 (#10670): only findUpSync is used (API
unchanged); no path-exists re-export usage; repo already requires
Node >=20.
- ts-morph 27.0.2 -> 28.0.0 (#10819): used only in apps/www; stable
core API (Project/createSourceFile/getSourceFile) unaffected by the
TS 6.0 internals change.
- @babel/core, @babel/parser, @babel/plugin-transform-typescript ->
7.29.7 (#10835): lockfile-only, existing ^7.26.0 ranges in
packages/cli already permit it.
Verified: root typecheck, CLI build, and runtime smoke tests for
find-up and ts-morph all pass.
* fix(dialog): correct default values for lazyMount and unmountOnExit
* refactor(typegen): extract default props programmatically from component source
- Remove manual static props JSON files for dialog, floating-panel, drawer
- Automatically extract defaultProps from component definitions at build time
- Ensures type definitions always reflect actual runtime defaults
- Eliminates documentation drift when defaults change in code
- Single source of truth reduces maintenance burden
Fixes#10861
* refactor(typegen): extract default props programmatically from component source
* refactor(typegen): extract default props programmatically from component source
* fix(orphaned-docs): resolved other remained untouched orphaned docs
* fix(www): map root provider defaultProps to RootProvider slot in typegen
Root providers/contexts carry no slot-name arg, so their defaultProps
were always written to the Root slot, leaving RootProvider stale.
Derive the slot from the variable name instead. Corrects
dialog/drawer/action-bar RootProvider lazyMount/unmountOnExit defaults.
---------
Co-authored-by: Lope <adebesintolulope80@gmail.com>
When typing in the Listbox Input to filter items, if no items match the
query, collection.items becomes empty. Accessing collection.items[0].value
on an empty array throws a TypeError. Add a null guard to fall back to
undefined defaultValue when the filtered collection is empty.
* chore(cli): migrate from deprecated tsconfck to get-tsconfig
* refactor(cli): skip unresolvable tsconfig references and expand test coverage
---------
Co-authored-by: Segun Adebayo <joseshegs@gmail.com>
* docs(www): add 3.36 FloatingPanel release blog and update homepage announcement
* docs(blog): add Splitter demos linking to the new docs sections
* docs(blog): set publishedAt to 3.36.0 release date
github-actions[bot]