What
Replace the $app/environment import in ChartList (ChartList.svelte, Row.svelte) with the framework-agnostic esm-env package (dev → DEV), and declare esm-env as a runtime dependency of @swr-data-lab/components.
Why
$app/environment is a virtual module that only exists inside SvelteKit. Because two components imported it, every non-SvelteKit consumer had to fake it: sophora-components carries a custom Vite resolveId shim, and Storybook only worked through @storybook/sveltekit's module mocking. esm-env (used by Svelte itself) provides the same flags through standard package export conditions and works in any bundler.
This removes the last SvelteKit runtime coupling from the published package and is a prerequisite for running Storybook on @storybook/svelte-vite (monorepo split) and for deleting the sophora shim.
Scope
Single change: two component files + one dependency entry. No behavior change (dev-flag semantics identical under Vite).
What
Replace the
$app/environmentimport inChartList(ChartList.svelte,Row.svelte) with the framework-agnosticesm-envpackage (dev→DEV), and declareesm-envas a runtime dependency of@swr-data-lab/components.Why
$app/environmentis a virtual module that only exists inside SvelteKit. Because two components imported it, every non-SvelteKit consumer had to fake it:sophora-componentscarries a custom ViteresolveIdshim, and Storybook only worked through@storybook/sveltekit's module mocking.esm-env(used by Svelte itself) provides the same flags through standard package export conditions and works in any bundler.This removes the last SvelteKit runtime coupling from the published package and is a prerequisite for running Storybook on
@storybook/svelte-vite(monorepo split) and for deleting the sophora shim.Scope
Single change: two component files + one dependency entry. No behavior change (
dev-flag semantics identical under Vite).