Resolve tailwind styles loss in bun environment #531
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
Change the export syntax in tailwind.config.js from CommonJS to ES modules. This modification fixes the issue of missing Tailwind CSS styles when running the application with bun. Signed-off-by: Ivan Li <ivanli2048@gmail.com>
|
Hi @IvanLi-CN Thank you very much for this. |
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.
Change the export syntax in tailwind.config.js from CommonJS to ES modules. This modification fixes the issue of missing Tailwind CSS styles when running the application with bun.
I've made some modifications and tested them successfully on Bun 1.1.29 and Node 18.20.2. While I haven't had the chance to test in other environments, I believe the changes should work well across the board.
In my opinion, these modifications are appropriate, but I'm open to feedback if I've overlooked anything. Please feel free to merge this PR if you find it suitable, or close it if you have any concerns.
For context, I've included the error message I initially encountered below.
Thank you for your consideration!