You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TL;DR The debugId is undefined for custom identifiers.
For context, I ran into this issue when authoring a component library using Vanilla-Extract. To repo this issue, I created a very simple Next.js app to illustrate the issue.
Describe the bug
I originally raised this issue on the Vanilla-Extract Discord server here. - https://discord.com/channels/885877446098964512/885877446891667529/1171464190200922152
TL;DR The
debugId
isundefined
for custom identifiers.For context, I ran into this issue when authoring a component library using Vanilla-Extract. To repo this issue, I created a very simple Next.js app to illustrate the issue.
Here is the Vanilla-Extract styling for the app.
With the above styling I would expect the
debugId
passed into the custom identifier to be'main'
however it isundefined
.This results in the CSS class name
undefined__b6xo1n
instead of the expectedmain__b6xo1n
.Reproduction
https://github.com/ufaubion-oracle/my-vanilla-app
System Info
Used Package Manager
npm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: