feat: add docs for registry

[shadcn]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
ui	✅ Ready (Inspect)	Visit Preview	Jan 16, 2025 7:08pm

[lloydrichards]

Been keeping an eye on registry development as it relates to #1561 so was excited to see some canary releases on this 🥳 . Since nothing has been officially been released I've been bumbling through the repository-template and created https://github.com/lloydrichards/shadcn-storybook-registry

But i've noticed some issues with the routed functions which I assumed was the preferred method to distribute, but am seeing only the public route being mentioned in the docs here.

• https://shadcn-storybook-registry.vercel.app/r/button-story.json <- this works as expected
• https://shadcn-storybook-registry.vercel.app/registry/button-story <- get a server error: ENOENT: no such file or directory, open '/var/task/registry/button.stories.tsx'
• https://raw.githubusercontent.com/lloydrichards/shadcn-storybook-registry/refs/heads/main/public/r/button-story.json <- also works

thought: with the registry function you might need to use process.cwd() in front of the specified file path 🤔

[shadcn]

@lloydrichards interesting. I see we're resolving the path with process.cwd() https://github.com/lloydrichards/shadcn-storybook-registry/blob/04f005e80d04c2b07e3f162d50cf27c5ee44c07d/app/registry/%5Bname%5D/route.ts#L42

what's the error in the logs?

[lloydrichards]

what's the error in the logs?

Locally it works as expected, get the JSON and everything good. But deployed in Vercel I get back as a response:

{
"error": "Something went wrong"
}

And in the vercel logs its reads:

Error processing component request: Error: ENOENT: no such file or directory, open '/var/task/registry/button.stories.tsx'
    at async (.next/server/app/registry/[name]/route.js:1:62728)
    at async tx (.next/server/app/registry/[name]/route.js:1:62649) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/var/task/registry/button.stories.tsx'
}

I ran into a similar issue once getting SQLite running on vercel, and the solution was to do with how the folder structure works in serverless, but I'm less sure here whats happeneing.

[lloydrichards]

just stumbled on the answer while checking what the file is was called:

https://vercel.com/guides/how-can-i-use-files-in-serverless-functions

Turns out you need to include the outputFileTracingIncludes config in the next.config.ts. see commit lloydrichards/shadcn-storybook-registry@e01e8c4

This fixes the routed version 👍

[shadcn]

@lloydrichards oh yeah you're right. I've done same as well but missed that in the docs. I'll fix.