Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support custom Tailwind config
See original GitHub issueI created custom config with colors like grey-900 but they where removed from styles.json.
I found this line in build.js /^bg-(transparent|black|white|gray|red|orange|yellow|green|teal|blue|indigo|purple|pink)/
I think it should be like this /^bg-/
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Configuration - Tailwind CSS
A guide to configuring and customizing your Tailwind installation.
Read more >Support for custom Tailwind configuration file paths - YouTrack
Custom configuration would allow me to tell the Tailwind CSS extension to auto complete from packages/popup/tailwind.config.js when working on ...
Read more >Tailwind CSS Configuration - Flowbite
Learn how to customize the default Flowbite and Tailwind CSS options and styles. ... You can easily do that by editing the tailwind.config.js...
Read more >Tailwind custom theme not working - RedwoodJS Community
When I made changes to the theme object in the tailwind.config.js file as below: theme: { extend: { colors: { primary: { light:...
Read more >Install Tailwind Config File to Add Custom CSS codes - YouTube
Welcome, How to Install Tailwind Config File to Add Custom CSS codes. Adding Tailwind Configuration File is must to add your own custom...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Is this also what’s causing e.g.
primary,secondary,dangeretc from being removed frombg-*styles? I can see it’s still generatingtext-primaryfor example, just notbg-primary.Actually, it could allow
bg-*classes, but filter out unsupported ones, but I think it will be a super ugly regex to have.