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.
Font weight not generated with removeFallbacks plugin
See original GitHub issueWith the removeFallbacks plugin, font-weight is not generated anymore since the update to tailwindcss 2.0 and xwind.
With the removeFallbacks plugin, twfont-bold emits an empty fontWeight object
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Font weight not working | WordPress.org
Hello,. I tried this plugin and it looks promising. I'm using Elementor for page building and applied default font weights. After creating a...
Read more >font-weight is not working properly? - Stack Overflow
I tried bold, bolder, 700, 800, 900 and is not working under FF. css · fonts · Share.
Read more >font-weight - CSS: Cascading Style Sheets - MDN Web Docs
The font-weight CSS property sets the weight (or boldness) of the font. ... If no match is found, look for available weights less...
Read more >csstools/postcss-font-weights - GitHub
Common font weights are found in the Font Weight Numeric Values section of the CSS Fonts Specification. Common Weight, Numeric Value. thin, 100....
Read more >Appendix | Font-Weight and Non-breaking Spaces - BEE Plugin
For example, a font family using the "Extra light" weight is often used to call out details not presented with the "Regular" variant....
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
@fknop Thanks! I was able to reproduce the bug by creating a CRA project. I’m releasing a fix soon! Yes, you are correct the fallback plugin didn’t handle numbers correctly.
@fknop should be fixed in the latest version (0.7.4)! Don’t forget to delete the
node_modules/.cacheagain to get a clean build. I recommend deleting the cache aftertailwind.config.jschanges or after updating packages until babel adds this PR to fix issue #8497.