maragudk / maragudk/gomponents-starter-kit
Setup Tailwid in JetBrains IDE is missing vital info
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 104
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
I wanted to setup Tailwind using CLI in my project but after following steps from the starter kit I encountered issues:
postcss-import: <path-to-tailwindcss>tailwindcss:105:78: Unclosed bracket
The language server is trying to parse the standalone CLI binary as CSS. When it resolves @import "tailwindcss" in tailwind.css, it finds the tailwindcss binary file sitting in the project root before it finds node_modules/tailwindcss. Pretty wild error. After renaming the binary to something else than tailwindcss it does indeed work correctly.
Also I found confusing the part that Tailwind has to be installed via npm in the project in order the Tailwind LSP to work. It wasn't clear at first to me that is necessary but a look at .gitignore helped me re-consider.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the starter kit's Tailwind CLI setup instructions, the referenced tailwind.css import, and .gitignore. Reproduce the JetBrains language server behavior with a root binary named tailwindcss, then verify the setup also explains the required npm installation. Done means the documented setup avoids the binary-resolution error and makes the dependency requirement clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tailwindcss
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100