Transpile import.meta.url in config files
#13322
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
RobinMalfait
approved these changes
Mar 22, 2024
|
Ah yeah will do! I'm testing the Standalone CLI to verify it works there too. |
thecrypticace
changed the title
import.meta is presentimport.meta.url in config files
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.
Right now if you try to use
import.meta.urlin atailwind.config.jsfile (or a dependency) Node will throw an error. This happens because config files are compiled to Common JS internally using Jiti and Sucrase. However, Sucrase doesn't rewriteimport.meta.urlso we must use Jiti's built-in Babel transform in this case.Fixes tailwindlabs/tailwindcss-intellisense#909