feat: export tailwindconfig tokens#720
Open
ruchamahabal wants to merge 1 commit into
Open
Conversation
Contributor
|
@ruchamahabal It's fine for now. Will have to find a better way when we migrate to Tailwind 4. |
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.
Move inline tokens to tailwind/tokens.js and export them from package.json to allow other projects to import and use them. Need this for Studio ref
I was using resolveConfig to do this earlier, but now it breaks because the preset in tailwindconfig imports
lucideIconsPlugin.js, which uses createRequire - a Node-only API that doesn't work in the browser. Also, it was not ideal to do so. Tailwind suggests writing tokens in a js file and using/exposing them for external use.If there is a better way to do this, please let me know
Coverage
mainBaseline pulled from the latest successful
mainrun.