Feature Request: Monorepo Support for Backend-Only Workspaces without Tailwind CSS

[Alwurts]

Feature Request: Shadcn/ui CLI Monorepo Support for Backend-Only Workspaces (without Tailwind CSS)

Context:

For a monorepo application with the following structure:

• apps/web (Next.js): Frontend application, using shadcn/ui components.
• apps/server (Express/HonoJS): Backend API server. This server does not use any UI components and therefore should not require Tailwind CSS.

I mantain a shadcn registry that has "blocks" examples that also install api route files simple-ai.dev app-01 block example

Problem:

The current shadcn/ui CLI, even with monorepo support, requires Tailwind CSS configuration in all workspaces. My apps/server only needs the API route files (e.g., route.ts) from a block, but there's no way to use the CLI without installing Tailwind and its configuration in the server package, which is undesirable.

Desired Feature:

I propose an enhancement to the shadcn/ui CLI's monorepo support to allow for "backend-only" workspaces. These workspaces would:

1. Skip Tailwind CSS Installation: The CLI should recognize that a workspace doesn't need Tailwind and avoid installing related dependencies or configurations. Perhaps a flag in components.json (e.g., "uiWorkspace": false) could indicate this.
2. Selective File Installation: The CLI should be able to install only the specified files needed for the backend. For example, only files with type: "registry:page" and a target pointing to the backend's directory structure should be installed in the backend workspace.
3. No Tailwind configuration: The components.json should not require tailwind configuration.

Example (app-01 block):

{
name: "app-01",
description: "A app with generative UI capabilities.",
type: "registry:block",
dependencies: [
	"ai",
	"@ai-sdk/openai",
	"zustand",
],
registryDependencies: [
	"avatar",
	"input",
	"label",
	`${BASE_URL}/r/chat-input.json`,
	`${BASE_URL}/r/chat-message-area.json`,
	`${BASE_URL}/r/chat-message.json`,
	`${BASE_URL}/r/jsx-renderer.json`,
	`${BASE_URL}/r/jsx-utils.json`,
],
files: [
	{
		path: "blocks/app-01/page.tsx",
		target: "app/generative-ui/page.tsx",
		type: "registry:page",
	},
	{
		path: "blocks/app-01/canvas/page.tsx",
		target: "app/canvas/page.tsx",
		type: "registry:page",
	},
	{
		path: "blocks/app-01/route.ts",
		target: "app/api/ai/generate/route.ts",
		type: "registry:page",
	},
	{
		path: "blocks/app-01/hooks/generation-store.ts",
		type: "registry:hook",
	},
	{
		path: "blocks/app-01/components/editor-layout.tsx",
		type: "registry:component",
	},
	{
		path: "blocks/app-01/components/editor-toolbar.tsx",
		type: "registry:component",
	},
],
categories: ["app"],
}

With the proposed feature, the CLI would:

• Install page.tsx and other component files into apps/web.
• Install only route.ts into apps/server.
• Not install any Tailwind-related files or configurations into apps/server.