| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
The new `django-tailwind` package comes with the Tailwind
CSS 4 by default, which migrated to the `postcss.config.js`.
|
| |
|
|
|
| |
This is copying some additions that tailwind-tools.nvim makes. There
are web frameworks such as Rails, Django, and older Phoenix that places
tailwind config files in asset folders.
|
| |
|
|
|
|
|
| |
tailwind-intellisense won't activate unless the filetype is detected
as an HTML-based file. Elixir `.ex` files can have `~H` sigils with
HEEX syntax inside or `~E` sigils with eelixir syntax. It's also typical
to have `.html.heex` files entirely of HEEX syntax. Both of these are
recognized in Elixir's tree-sitter injections.scm
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Enhance root directory detection for the latest versions of
TailwindCSS v4, which no longer require tailwind.config.* or
postcss.config.*.
For Phoenix projects, they are typically generated or add Tailwind
installed via https://github.com/phoenixframework/tailwind which will
now be detected by scanning the mix.lock file for the included package.
Phoenix projects that install tailwindcss via package.json should still
work.
|
| | |
|
| |
|
