Add legacy type exports to tailwindcss/plugin export
#16505
Merged
+13
−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
philipp-spiess
force-pushed
the
fix/add-legacy-type-exports-to-plugin-module
branch
from
23ec7c0 to
2bf8975
Compare
RobinMalfait
approved these changes
Feb 13, 2025
philipp-spiess
deleted the
fix/add-legacy-type-exports-to-plugin-module
branch
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.
Closes #16209
This PR exposes the following types that were accessible via
tailwindcss/types/configin v3 now via thetailwindcss/pluginexport:Note that these types will not be the same as the v3 and just approximations, however it should be enough to upgrade plugins to work with v4.
Test plan
Tested in a standalone project importing a dev build of tailwindcss: