Skip to content
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

Question: Non-autocomplete twind extension #1519

Closed
sebastiandotdev opened this issue Jul 24, 2023 · 11 comments
Closed

Question: Non-autocomplete twind extension #1519

sebastiandotdev opened this issue Jul 24, 2023 · 11 comments

Comments

@sebastiandotdev
Copy link

Good afternoon, deno fresh community this issue should not be here but I take the trouble to ask Why I do not want to autocomplete the twind classes

extesion

code

What a shame my ignorance and thank you for your attention

@afifurrohman-id
Copy link

afifurrohman-id commented Jul 25, 2023

Me too, alternatively you can create empty file tailwind.config.ts in root project directory and using tailwind extension instead twind

@sebastiandotdev
Copy link
Author

Do you recommend it for style development, do you have any configuration in the file or is it simply empty?

@afifurrohman-id
Copy link

afifurrohman-id commented Jul 26, 2023

Only empty file, just for tailwind extension auto complete, for config keep using twind.config.ts and ignore it using .gitignore

But this tailwind extension is not 100% compatible with twind v0,

so you can use twind v1 and it's work fine like tailwind, tutorial already included in fresh docs here

@afifurrohman-id
Copy link

afifurrohman-id commented Jul 26, 2023

I also using in my personal project if want to see more details examples here

@sebastiandotdev
Copy link
Author

sebastiandotdev commented Jul 26, 2023

Captura de pantalla 2023-07-26 090504
Thank you very much mate, it worked

@sebastiandotdev
Copy link
Author

In this case the tailwindcss extension is activated, right?

@willpuckett
Copy link

It seems like it would be nice to be able to use the twind extension, but seeing the color previews in the tailwind version is kinda nicer anyway

@u-yas
Copy link

u-yas commented Sep 9, 2023

I think the workaround introduced here is the best.

tw-in-js/vscode-twind-intellisense#9 (comment)

@anilanar
Copy link

anilanar commented Nov 6, 2023

I think the main confusion stems from the fact that some people use tailwind extension while others use twind extension. Possibly, most people don't even know that they are different.

In my case, I couldn't make twind extension have autocompletes. The twind extension output has pretty much nothing even with debug: true. It seems twind extension is pretty much dead, with bunch of issues left open.

It would be great to update the project scaffold to either suggest a better extension that works, or use something else than twind.

@marvinhagemeister
Copy link
Collaborator

@anilanar We're in the process of moving away from twind. There is both a proper Tailwind CSS plugin in development as well as one for UnoCSS.

@marvinhagemeister
Copy link
Collaborator

Closing this as we've switched to Tailwind CSS which allows us to compile the style sheet ahead of time and move it out of the render path. The Tailwind CSS plugin will be released in the next Fresh 1.6 version which I'm hoping to release later this week.

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

6 participants