Add type declaration #118
Merged
Add type declaration #118
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
- This way it doesn't rely on the `@types/tailwindcss` Definetely Typed repo which could cause issues when we release Tailwind CSS 3.1 with our own types. - Use `export = plugin` instead of `export default plugin` so that it is compatible with `module.export`
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Closed
This was referenced May 18, 2024
This was referenced May 25, 2024
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 is a continuation of #117 with a few changes. These changes include:
@types/tailwindcssDefinetely Typed repo which could cause issues when we release Tailwind CSS 3.1 with our own types.export = plugininstead ofexport default pluginso that it is compatible withmodule.exportwhich is what most people use.Closes: #117