Not working for HTML-like files

[SHxKM]

Thanks for the great extension.

For regular HTML files, it works great. However, the extension stops working completely once a file is associated via VSCode to another file type.

For example, Django template files use the regular .html extension but include special mustache {{ }} syntax. I'm using another extension to get tag highlighting for these files, as well as emmet expansion. But once I associate this file as "Django HTML" - TailwindCSS Intellisense stops working.

Anything I'm missing?

[SHxKM]

Poking in the code, could it be as simple as adding "django-html" to this list in this file in src/index.ts?

https://github.com/bradlc/vscode-tailwindcss/blob/dd82e0282e03f6832f18976718f036050fe57ecc/src/index.ts#L40-L61

Perhaps it's better to make this list extensible through a setting?

[JulioBarros]

Doesn't work for me for .jsx files. Would be great if that could work too. Thanks.

[alpap]

same here for svelte files

[dhc02]

I'm pretty sure @SHxKM's suggestion should work for django, and a similar simple change should work for most other html-like files.

As you can see from #18 , that's all it took to make this work for Phoenix last year.

I think that what we need is a setting for the extension that can be modified by users to add other filetypes so that it's not hard-coded in the extension, requiring a pull request for every addition.

This would be similar to how PHP Intelephense does it: In your settings.json, you can add

"intelephense.files.associations": [
    "*.php",
    "*.phtml",
    "*.myRandomFiletype"
  ]

and then it will start treating .myRandomFiletype as php.

I've looked into the code for this extension and I can't wrap my head around how to implement something like this yet. What do you think, @bradlc?

[rhyswat]

Ditto when I've told VS Code to treat foo.css as PostCSS. I get completions for foo.css as CSS.

Extension version 0.2.0

VS Code version 1.36.1

[ryudice]

It's not working on js and jsx files

[pavelloz]

I have the same problem, but in .liquid files. Maybe it would be nice to just have an option that you place under a language that enables plugin.

ie.

    "[liquid]": {
        "tailwindcss.enabled": true
    },

Anyway, since author is not responding and this is very easy fix + pretty much a blocker, probably forking is the way to go.

[skycult]

It does not works for any Vue + Tailwind project.

[pavelloz]

BTW. @skycult make sure you have config file in your project.

When i was tuning forked extension for my use case i discovered https://github.com/bradlc/vscode-tailwindcss/blob/master/package.json#L25-L27 which means extension wont even activate until you have a tailwind config.

[kamalhm]

@pavelloz

I've added the tailwind config but it still doesnt show up on vue-file, any suggestion?

[reducio]

I have problem with .html.eex and .html.leex files in Phoenix (Elixir).

If changing the VSCode file type (lower right hand corner of window) to HTML manually when editing tailwind classes which is annoying but does work.

So I can see this extension support HTML (EEx): https://github.com/bradlc/vscode-tailwindcss/blob/f5dfe02f74ac9bd68529f1997ae875691b819833/src/index.ts#L50

Check topic on the ElixirForum, please: https://elixirforum.com/t/how-to-force-the-tailwind-css-intellisense-extension-for-vscode-work-with-html-eex-and-html-leex-files/25520

[reducio]

I have problem with .html.eex and .html.leex files in Phoenix (Elixir).

If changing the VSCode file type (lower right hand corner of window) to HTML manually when editing tailwind classes which is annoying but does work.

So I can see this extension support HTML (EEx):

https://github.com/bradlc/vscode-tailwindcss/blob/f5dfe02f74ac9bd68529f1997ae875691b819833/src/index.ts#L50

Check topic on the ElixirForum, please: https://elixirforum.com/t/how-to-force-the-tailwind-css-intellisense-extension-for-vscode-work-with-html-eex-and-html-leex-files/25520

SOLUTION: https://elixirforum.com/t/how-to-force-the-tailwind-css-intellisense-extension-for-vscode-work-with-html-eex-and-html-leex-files/25520/4?u=stavanger

[jrock2004]

It would be awesome of we could add our list of filetypes because I think it would be bad for the maintainer of the plugin to have to add them all. The real logic seems to be in tailwindcss-language-server which seems to be private. Would be awesome to hear from main developer on if he would like help implementing something or are we all stuck with the ext he has chosen?