feat: generate CSS exports when css.splitting is disabled#680
Merged
sxzz merged 10 commits intorolldown:mainfrom Jan 1, 2026
Merged
feat: generate CSS exports when css.splitting is disabled#680sxzz merged 10 commits intorolldown:mainfrom
css.splitting is disabled#680sxzz merged 10 commits intorolldown:mainfrom
Conversation
✅ Deploy Preview for tsdown ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
commit: |
3d3f0b2 to
b1ac8c2
Compare
7793350 to
61ca7eb
Compare
sxzz
requested changes
Dec 31, 2025
sxzz
reviewed
Jan 1, 2026
sxzz
approved these changes
Jan 1, 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
2 participants
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.
Description
Automatically generates CSS exports in
package.jsonwhencss.splittingis disabled. This enables component libraries to bundle CSS into a single file and expose it via package exports for users to import.Additional context
generateExportsnow accepts a singleoptionsobject (containingexports,logger,css,outDir) instead of separateExportsOptionsandloggerparameters. This change enables future extensions where exports generation depends on multiple configuration options.