Replies: 1 comment
-
|
it looks like I can do this by file: This seems to avoid generating the bulk of it. it will still pick up additional css if the file contains a mixture of both old and new. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I am working on migrating from chakra-ui v2 to panda-css.
Because chakra-ui and panda/ark share a lot of the same tag names (Box, Flex, Heading, etc) the chakra-v2 components end up getting styles extracted for them.
Code:
Here is the debug AST for the specific file:
Looking at the docs I see https://panda-css.com/docs/concepts/hooks#configuring-jsx-extraction, but the arguments to write a custom rule don't seem to include additional details about which package the tag came from.
Is there anyway to avoid extracting styles for tags that share the same name? I think in our case at least if we had access to the import package during the
parser:beforehook we should in theory be able to exclude the chakra-v2 code.Beta Was this translation helpful? Give feedback.
All reactions