fix(smrt-svelte): publish import conditions for svelte exports

[willgriffin]

Summary

• add explicit import conditions to @happyvertical/smrt-svelte export entries alongside the existing svelte condition
• keep the package surface unchanged while making the published metadata match the rest of the SMRT Svelte packages
• address the consuming Vite/SvelteKit dev runtime failure we hit in anytown.ai

Problem

In anytown.ai after bumping to @happyvertical/smrt-svelte@0.21.16, the dashboard dev server started logging a Vite/PostCSS internal error while loading package styles from @happyvertical/smrt-svelte, for example:

.../dist/components/forms/Select.svelte?svelte&type=style&lang.css: Unknown word Snippet

That symptom came from Vite trying to treat the raw .svelte source as plain CSS instead of honoring the Svelte package entrypoint metadata.

smrt-svelte was the outlier here: its exports only published default for the JS entrypoints, while other SMRT Svelte surfaces publish explicit import conditions.

Testing

• pnpm -C packages/smrt-svelte check
• pnpm -C packages/smrt-svelte build
• re-ran the anytown.ai dashboard route load against this patched package metadata and the earlier smrt-svelte CSS parse error no longer appeared in the Vite server log

[Copilot]

Pull request overview

This PR updates @happyvertical/smrt-svelte’s published exports metadata to include explicit "import" conditions alongside existing "svelte" conditions, aligning it with the other SMRT Svelte packages and preventing Vite/SvelteKit from mis-resolving Svelte sources as plain CSS.

Changes:

• Added "import" conditions for the root export and each Svelte component subpath export.
• Added "import" conditions for ./registry, ./themes, and ./browser-ai entrypoints where applicable.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.