Is @ark-ui/anatomy deprecated in favor of using the component libs?

[caseybaggz]

We use the @ark-ui/anatomy package in our panda-preset trying to stay component agnostic but that lib seems to be very outdated on zag deps which is causing some high-severity security issues for our team.

Thus, I couldn't find the source anywhere - only the component libs which we resorted to using the /react which I don't love since we are moving to SolidJS and will have both React/Solid libs in our near future.

I do understand the maintainability ease of just throwing it into the component libs but I did appreciate the original not being tied to a component library.

Does anyone know where that workspace exists in the repo or if it was killed off?

[cschroeter]

@caseybaggz

Thanks for reaching out. Atm, the only way is to import a component's anatomy directly from the framework package, e.g.:

import { Avatar, avatarAnatomy } from '@ark-ui/[solid|react|vue]/avatar'

Since the components are fairly stable, hardcoding the parts as you style them should also be fine.

[caseybaggz]

Thanks @cschroeter for the quick response and clarity.

We did use to hardcode them but switched to the anatomy for our components that we have migrated to Ark so there is the clear connection between what is Ark and what is our own content. Likewise, now that we have a large set of recipes, refactoring back to static arrays is not an option.

However, this is not a deal breaker at all. I think it will be fine since we use JSR and everything is code split. Will keep you posted if we run into problems using a specific library package in our preset when shipping the recipe in an opposing library.

Side note, I did notice that we actually ran into type errors when using the component specific path you mentioned. I'm having to use the global path to get access to the <component>Anatomy helper to prevent that.