v0.1.17

chore: bump to 0.1.17

v0.1.16

feat: smart dev server restart for component overrides

- Scan dashboard source at startup to build knownDashboardComponents set
- Track appliedOverrides dynamically during esbuild pre-bundling
- File watcher only restarts Vite when override files change:
  - ADD: restart if name matches a known dashboard component
  - CHANGE: restart only if it's an active override
  - UNLINK: restart only if it was an active override
- No hardcoded lists — everything is scanned dynamically

Bump to 0.1.16

v0.1.15

Fix: Recursive component overrides

The published 0.1.14 dist was missing the recursive collectComponentFiles scan. Component overrides
placed in subdirectories of src/admin/components/ were silently ignored. This release fixes that —
nested overrides now work as documented.

Docs: Menu, nested routes and modules interaction

New documentation section in README explaining:

• How nested in defineRouteConfig() auto-injects routes into the sidebar
• How to prevent duplicates between menu.config.tsx and nested routes
• How plugin modules (e.g. @medusajs/draft-order) interact with the custom menu vs the Extensions
  section

v0.1.14

What's new

• Recursive component overrides — the vite plugin now scans the entire src/admin/components/
  tree, not just the root level. Organize your overrides in subdirectories.
• Trusted Publishing — publish workflow now uses npm OIDC (no token/OTP needed).
• Multi-package-manager docs — installation instructions for Yarn, npm, and pnpm.
• Added author, homepage, and bugs metadata.