Open
Description
Feature description
Current documentation of custom registry suggests
Imports should always use the @/registry path
What is not that explicit and expected is for imports like @/registry/lib/abc
or @/registry/hooks/abc
will also be transformed into <@/component>/abc
, per alias <@/component> configured
Not sure if that is intended (which we could improve docs), in our use case we do need to support other types and happy to PR
Affected component/components
custom registry
Additional Context
Additional details here...
Before submitting
- I've made research efforts and searched the documentation
- I've searched for existing issues and PRs
Activity