Skip to content

Regression in v0.14.7: Font weight reset of defaults in @theme shows errors #1236

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

Closed
ADTC opened this issue Feb 26, 2025 · 5 comments · Fixed by #1237
Closed

Regression in v0.14.7: Font weight reset of defaults in @theme shows errors #1236

ADTC opened this issue Feb 26, 2025 · 5 comments · Fixed by #1237
Assignees
Labels
bug Something isn't working

Comments

@ADTC
Copy link

ADTC commented Feb 26, 2025

With the update to v0.14.7, the following line, and all lines below it, are showing errors.

--font-weight-*: initial;

Removing the above line also resolves all errors in subsequent lines below it. The CSS itself is valid, and works correctly with Tailwind. This is a problem with the VS Code extension.

Screeshots:

Image Image Image

Regression

This worked fine until v0.14.6 where there were no errors. See screenshot when the older version is installed:

Image

Current workaround: Downgrade to v0.14.6 and disable auto-update until this is resolved.

Additional Information

This doesn't happen with other resets above the font weight reset. I have several others above it, like:

--color-*: initial;
--breakpoint-*: initial;
--radius-*: initial;
--shadow-*: initial;
--font-*: initial;
--font-weight-*: initial; /* <-- Errors in v0.14.7 start here. */

If I move the font weight reset to be the first line in the @theme block, then everything below it gets errors, including all those other resets.

It looks like a parsing problem when there are two words instead of just one. For example, if I change the color reset to --color-test-*: initial; it starts having the same error too.

@thecrypticace
Copy link
Contributor

🤦‍♂ of course I forgot a - somewhere… will get this fixed today.

@thecrypticace
Copy link
Contributor

Gonna get a new release out in the next hour or two 👍

@ADTC
Copy link
Author

ADTC commented Feb 26, 2025

Thank you for the quick action @thecrypticace

@thecrypticace
Copy link
Contributor

That release should be out now btw

@ADTC
Copy link
Author

ADTC commented Feb 28, 2025

Thank you. Got it, and it's working perfectly.

BTW, you tagged the new release v0.14.8 but forgot to make it a "Release" on GitHub. Just letting you know 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
2 participants