chore: replace package build setup with tsdown - #3571
Open
jpzwarte wants to merge 41 commits into
Open
Conversation
🦋 Changeset detectedLatest commit: 92e1bef The changes in this PR will be included in the next version bump. This PR includes changesets to release 72 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
a11ymiko
approved these changes
Aug 11, 2026
michal-sanoma
approved these changes
Aug 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #3182
Closes #3569
Replaces the esbuild package build with tsdown and upgrades the Angular wrappers to Angular 22.
Packaging
dist/; the packages are now resolved entirely throughexports.main,moduleandtypesare dropped —exportsalready points at the JavaScript, and TypeScript picks up the adjacent.d.tsfrom there.exportsandpublishConfig.exportsare generated by tsdown from its entry list — change the build config, not the exports map by hand.index.ts/register.ts) move intosrc/. Styles move from.scssto.css, imported withwith { type: 'css' };Angular
Angular 21 → 22, builders moved to
@angular/build,^22.0.0added to the peer range alongside 19–21.Fixes
sideEffectsstill listedregister.js, which matches neithersrc/register.tsnordist/register.jsunder the new layout. Bundlers were silently tree-shaking away everyimport '@sl-design-system/*/register.js', leaving the custom elements unregistered.package.jsonacross 18 packages, plus missing peers (@open-wc/scoped-elements,@lit/localize,lit).format-date/format.js,grid/utils.jsandlocales/*.xlfsubpath exports that the generated exports map had dropped.isDevMode()(@sl-design-system/shared/dev-mode.js), replacing the/// <reference types="vite/client" />iniconandcomboboxthat leaked an empty*.cssambient module into every consumer's TypeScript program.examples/litto.cssas well, and teach the website's esbuild config to handlewith { type: 'css' }.