Remove useless console.log in @tailwind/vite package
#16307
Merged
+0
−1
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
RobinMalfait
approved these changes
Feb 6, 2025
3 tasks
|
How is it even possible that no one noticed this?
I asked about this here: #16321, So I'm curious does anyone here even use TailwindCSS with Vite? |
Well, a lot of people are using but console logs are just tiny iceberg IMO. See this for example nuxt/ui#3275 :) Thanks! |
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.
This PR removes a (seemingly) unwanted
console.login the@tailwind/vitepackage.I discovered this when I updated tailwind in my
astroproject, each.astrocomponent log the full path of an imported.cssfile.It seems that this was the commit that introduced it: e1a85ac