Enrico Sacchetti

This is a suggestion worth considering.

Thanks, this came to our attention back when it was added in: https://github.com/carbon-design-system/carbon-components-svelte/pull/1627#pullrequestreview-1250712327 A potential replacement could be https://github.com/absolute-version/commit-and-tag-version

Perhaps we can include this change as part of the v11 upgrade, assuming the flagship library adopted this behaviour in v11.

Agreed, #156 should resolve this. The main issue is with projects using a mix between named imports and deep imports may cause performance issues in dev mode. With the new...

Seeing that the core React library doesn't have a `minCount` prop, this requires upstream designs. I recommend opening a ticket in https://github.com/carbon-design-system/carbon/issues to kick off this functionality.

I recommend including "different handling of nested CSS" as part of breaking changes. Svelte 5 makes use of `:where()` for nested selectors (for both Runes and non-Runes modes) while Svelte...

A follow up to https://github.com/sveltejs/svelte/issues/11400#issuecomment-2106447712: I see that `:where` is only applied to Nested CSS, and not *all* scoped CSS. Current documentation reads (emphasis mine): > To avoid issues caused...

Perhaps like this: ```diff -To avoid issues caused by unpredictable specificity changes, scoped CSS selectors +To avoid issues caused by unpredictable specificity changes, nested CSS selectors now use `:where(.svelte-xyz123)` selector...

In my related comment, I suggested using Skypack to help with package compatibility: https://github.com/sveltejs/sites/issues/137#issuecomment-1360763974

I also recommend adding pagination and streaming (or conditional streaming) to help with profile load performance.