Falsy values in tailwind config trigger class not found about twin.macro HOT 7 CLOSED

Hey Vincent, thanks for looking into this and it's great you got to the bottom of it.
I think adding a value of 0 should be allowed so I'll add a fix for this 👍

Were you able to trigger the error consistently?

from twin.macro.

If I can help you testing your fix, don't hesitate to sollicitate me :)

from twin.macro.

This bug was fixed in v1.0.0 🎉

from twin.macro.

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?

from twin.macro.

I debugged a little, and got the issue.

The inset config for zero value should be '0': '0', not '0': 0. Otherwise, the lookup here will fail as the '0' config value as a number, extracted from the classParts will be evaluated as a falsy value... And because the lookup fails, the resolve function returns an empty object triggering the error even if the class exists in the Tailwind configuration.

This was this dumb lol.

I'll let you close the issue if you don't think it is necessary to add any safeguard 😊

from twin.macro.

Apart from cache issues, yes !
Everytime I switch back from '0' or '0px' to 0 while clearing node_modules/.cache folder and restarting Gatsby server (due to config livereloading issues), the error comes back.

from twin.macro.

great, that'll help me out testing a fix - thanks so much for submitting the issue :)

from twin.macro.