shadcn-ui
docs(www): add deno commands to docs
Display deno commands in npm command blocks of the documentation.
These commands work, and Vite + shadcn is runnable in Deno (as long as a package.json is used).
@alexgleason is attempting to deploy a commit to the shadcn-pro Team on Vercel.
A member of the Team first needs to authorize it.
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Updated (UTC) |
|---|---|---|---|
| ui | ✅ Ready (Inspect) | Visit Preview | Apr 23, 2025 0:21am |
| v4 | ✅ Ready (Inspect) | Visit Preview | Apr 23, 2025 0:21am |
I'm unclear if this should be apart of this PR or not, you mentioning updating the tsconfig.json, its a best practice that when you are working in Deno both your package.json and tsconfig.json get moved into your deno.json file. The strucutre of this file is similar to how the tsconfig.json is strutured
Display deno commands in npm command blocks of the documentation.
These commands work, and Vite + shadcn is runnable in Deno (as long as a package.json is used).
Love this as I use Deno heavily in my projects. I wanted to ask around if this PR should also mention using your deno.json file instead of adding directives to your tsconfig.json? It isn't common with Deno projects to have a tsconfig.json file
