-
-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Falsy values in tailwind config trigger class not found #41
Comments
Great to hear you're enjoying twin! - Aside from the bug you've found anyway 😄 I haven't seen this specific bug before but I am aware of some caching issues, particularly in Gatsby. I've made a codesandbox attempting to reproduce the issue but haven't succeeded yet. Perhaps you could verify the tailwind.config.js is the same? Or if there's any other plugins that could be interfering. Also another thought - is the error still showing after you do a gatsby build? |
I debugged a little, and got the issue. The inset config for zero value should be This was this dumb lol. I'll let you close the issue if you don't think it is necessary to add any safeguard 😊 |
Hey Vincent, thanks for looking into this and it's great you got to the bottom of it. Were you able to trigger the error consistently? |
Apart from cache issues, yes ! |
great, that'll help me out testing a fix - thanks so much for submitting the issue :) |
If I can help you testing your fix, don't hesitate to sollicitate me :) |
This bug was fixed in v1.0.0 🎉 |
Hello there,
First of all, thanks for this library. Even though it's still young, it is showing promising things and I'm eager to see future releases !
I'm posting due to a weird issue I'm encountering on my GatsbyJS project.
I have setup a project as stated in the docs, and am using Twin with Emotion.
I've customized the "inset" section of my Tailwind theme as is :
inset: { '0': 0, auto: 'auto', 'icon-offset': '19px', }
From time to time, I don't know why it doesn't always occur, I'm getting this error message and my bundle no longer builds :
I've tried restarting the dev server, clearing the .cache folder inside node_modules, nothing helps. I can sometimes get rid of the error by removing all inset classes from the incriminated file and let livereloading do its job.
Any ideas why this happens ?
Let me know if I can help you with anything by providing you any specific details.
The text was updated successfully, but these errors were encountered: