andre_br
Phoenix 1.8.1 and TailwindCSS/daisyUI IntelliSense autocomplete suggestions on vscode
Hello Folks,
We’re working on a Phoenix 1.8.1 new codebase, and loving to have the native DaisyUI component library available that comes out of the box with it.
But with Phoenix 1.8 came along an issue that was vscode’s Intellisense extension not suggesting anymore the classes names that it does at Phoenix 1.7.x codebases.
As for the TailwindCSS classes names, we managed to solve it by creating a blank assets/tailwind.config.css file, that, just by existing, seems to have made Intellisense aware that there’s TailwindCSS around here. ![]()
But as for the DaisyUI classes names, we still can’t find the solution to make Intellisense suggest them. The only options that it gives are the TailwindCSS native classes. And it would be awesome to see there also the DaisyUI component classes.
Did anyone run into this and could share the approach to get it working?
Thanks a lot, folks!
André
Most Liked
rhcarvalho
I don’t know of any workaround. This is the upstream issue to subscribe to: Plugins can't import `tailwindcss/plugin` when using Standalone CLI or CDN · Issue #1301 · tailwindlabs/tailwindcss-intellisense · GitHub
arcanemachine
Last Post!
dunyakirkali
Popular in Questions
Other popular topics
Latest Phoenix Threads
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #hex
- #security









