Re-add possibility to add CSS prop #169
Merged
Conversation
This file contains 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
Closed
Mad-Kat
force-pushed
the
features/swc-css-prop
branch
from
15e7ba5 to
dba7ba6
Compare
jantimon
approved these changes
Nov 8, 2024
|
Released in next-yak 2.3.0 |
jantimon
pushed a commit
that referenced
this pull request
Nov 8, 2024
Co-authored-by: Luca Schneider <[email protected]>
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.
With the move to the SWC plugin we lost the ability to transform css properties (#78).
This PR re-adds the possibility to use
next-yakwith css propsStill to discuss: