[Registry] Configure aliases/folders for custom registry

[peterkogo]

We are hosting our own shadcn components over at React Flow, which arguably is a little different from other general purpose components built with the shadcn cli. (it sometimes requires an additional step after installing the package to wire it up with React Flow or use it in the correct context).

Anyway, working in a bigger project with all kinds of shadcn and React Flow components, things get cluttered pretty fast as everything added through the shadcn add just lands (more or less) in the same folder. I saw that there is a target property but it get's only respected for files and pages...

It would be cool to just define a folder where components from a specific registry end up in. Even cooler would be the ability to define aliases in the components.json for certain registries.

[b3nab]

I was kinda thinking that the CLI needs something like that. In some way to be extensible like adding custom path aliases that may be picked up by the target property.

Something like:

{
  "$schema": "https://ui.shadcn.com/schema.json",
  "style": "default",
  ...
  "aliases": {
    ...
    "custom": "@/custom",
  }
}

And then in the registry.json of custom registries we can use it like the following:

{
  "$schema": "https://ui.shadcn.com/schema/registry.json",
  ...
  "items": [
    {
      "name": "my-complex-stuffs",
      "type": "registry:block",
      ...
      "files": [
        {
          "path": "registry/default/ultra/complex/component.tsx",
          "type": "registry:block",
          "target": "#custom/component.tsx"
        },
        ...
      ]
    }
  ]
}

Things to note in the latest target it could be used @ but it can be used any other char, like # to differentiate it from the typescript paths alias.

I think this way it could be a more nice experience for developers on both sides.