Skip to content

Add support for v4 fallback #1157

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Feb 4, 2025
Merged

Add support for v4 fallback #1157

merged 5 commits into from
Feb 4, 2025

Conversation

thecrypticace
Copy link
Contributor

@thecrypticace thecrypticace commented Jan 30, 2025

Closes #1145

Right now this doesn't support the use of JS APIs. That's proving to be a bit more of a complicated task since we're using ESM to load stuff. Jiti complicates things a bit there too.

I think I'm comfortable shipping an initial version that doesn't support doing something like import plugin from 'tailwindcss/plugin' in plugins and configs.

@thecrypticace thecrypticace force-pushed the feat/v4-fallback branch 2 times, most recently from 3579f16 to 336ff76 Compare January 30, 2025 16:40
Ideally we would never need this but Vitest hooking into imports and stuff makes this necessary to properly test a small number things w/o outside interference
This does not currently support importing / requiring JS APIs when configs and/or plugins are used.
@thecrypticace thecrypticace marked this pull request as ready for review February 3, 2025 23:50
Copy link
Member

@philipp-spiess philipp-spiess left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good stuff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Suggestions for Tailwind CSS v4 are not provided when using the Standalone CLI
2 participants