You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
#602 goes through the trouble of adding a type hint to the Prettier config in the Tailwind installer, but the installer doesn't add the prettier type definitions to the project, thus leaving the type hint unable to resolve, i.e. not giving the convenience of auto-completion in VS Code.
Note: The Prettier VS Code extension doesn't seem to automatically provide auto-completion in the Prettier config file when it is named.prettierrc.cjs. I guess this is why the type hint was added in the first place. I wonder if having these type definitions globally installed fix this issue, but I feel like that's the wrong solution.
Describe the solution you'd like to see
The Tailwind installer adds the @types/prettier dependency to the project
Describe alternate solutions
Maybe a comment in the Prettier config file hinting at installing the package?
In an ideal world, I'd like to see Prettier put these type definitions directly into their package (rather than DefinitelyTyped) but I feel like that's not likely to happen for a while
Additional information
No response
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
#602 goes through the trouble of adding a type hint to the Prettier config in the Tailwind installer, but the installer doesn't add the prettier type definitions to the project, thus leaving the type hint unable to resolve, i.e. not giving the convenience of auto-completion in VS Code.
Describe the solution you'd like to see
The Tailwind installer adds the
@types/prettier
dependency to the projectDescribe alternate solutions
Maybe a comment in the Prettier config file hinting at installing the package?
In an ideal world, I'd like to see Prettier put these type definitions directly into their package (rather than DefinitelyTyped) but I feel like that's not likely to happen for a while
Additional information
No response
The text was updated successfully, but these errors were encountered: