Skip to content

"Unknown utility" TS warning on certain class names #174

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

Closed
bryceknz opened this issue Apr 6, 2021 · 6 comments
Closed

"Unknown utility" TS warning on certain class names #174

bryceknz opened this issue Apr 6, 2021 · 6 comments

Comments

@bryceknz
Copy link

bryceknz commented Apr 6, 2021

Since migrating to Twind, I have noticed some class names throwing TS warnings.

This is by no means an exhaustive list, but I've noticed them on the following class names:

  • flex-gap-4
  • mx-auto
  • mt-auto

Screenshots:

image
image

@lukejacksonn
Copy link

Thanks for reporting this, I think flex-gap is a missing custom plugin type definition. The margin errors should come with the Twind dev tools so will try get a fix in for that asap 👍

@sastan
Copy link
Collaborator

sastan commented Apr 6, 2021

@bryceknz Which twind version are you using? The margin errors should be fixed in one of the latest version (currently in mobile, can not check which version).

@bryceknz
Copy link
Author

bryceknz commented Apr 6, 2021

Hi @sastan, thanks for that info! I'm running 0.16.7, I can see now that it's resolved in a later release, cheers! 🎉

@redbaron76
Copy link

I'm using the next branch and it's still present in most of the tw classes.
And I've noticed that neither VSCode Tailwind official plugin nor Twind plugin are working as expected.

Is it something broken or am I doing something wrong / not enabling something?

@sastan
Copy link
Collaborator

sastan commented Mar 16, 2022

The VS-Code and the typescript plugin haven't been updated to work with the next branch. That is still an open issue.

@IgnusG
Copy link
Contributor

IgnusG commented Mar 16, 2022

I'm using the next branch and it's still present in most of the tw classes. And I've noticed that neither VSCode Tailwind official plugin nor Twind plugin are working as expected.

Is it something broken or am I doing something wrong / not enabling something?

Support for v1 for intelli tracked in tw-in-js/vscode-twind-intellisense#7 I believe

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

No branches or pull requests

5 participants