Fixes
- specializer: read what a library's barrel exports, whatever its shape
- specializer: read a prop
export { … as … }renames
Performance
- load the parser only when a build starts (~21.3 → ~17.4 ms import)
- make the size formatters on first use (~17.4 → ~7.3 ms import)
The shared analysis behind optimizeCss({ propAware: true }) and optimizeComponents only followed export { default as X } from "./X.svelte" barrels. Libraries that use export *, namespace re-exports (<Button.Root>), or Object.assign(Root, { Item }) had call sites the analysis never saw. Prop renames like export { fore as for } were kept under the internal name, so <Label for="e"> read the default.
optimizeCss({ propAware: true }) / optimizeComponents()
- Each name the app imports from the library barrel resolves to a component, an object with component members, a non-component value, or unknown (keeps every component).
- A prop re-exported under another name is read as the public name Svelte 3–5 expose.
Loading svelte.config.js (vite, svelte-check, the language server) no longer pulls in the parser or ICU number data up front:
| v0.11.54 | v0.11.55 | |
|---|---|---|
Median dist/index.js import (Node, 15 fresh processes)
| ~21.3 ms | ~7.3 ms |