Repository: ui
Issue: [bug]: CLI doesn't respect tsconfig -> references, following installation docs for vite+react is wrong; npx shadcn@latest add doesn't respect --path
Labels: bug

### Describe the bug

There are two issues here:

1. Following the [installation instructions for vite](https://ui.shadcn.com/docs/installation/vite) step-by-step, trying to run `npx shadcn@latest init` fails complaining about being unable to find import aliases. The root issue here appears to be that the create vite script (react+typescript template) creates three tsconfig files:

```json
// tsconfig.json
{
  "files": [],
  "references": [
    {
      "path": "./tsconfig.app.json"
    },
    {
      "path": "./tsconfig.node.json"
    }
  ]
}
```

```json
// tsconfig.app.json
{
  "compilerOptions": {
    "target": "ES2020",
    "useDefineForClassFields": true,
    "lib": [
      "ES2020",
      "DOM",
      "DOM.Iterable"
    ],
    "module": "ESNext",
    "skipLibCheck": true,
    /* Bundler mode */
    "moduleResolution": "bundler",
    "allowImportingTsExtensions": true,
    "isolatedModules": true,
    "moduleDetection": "force",
    "noEmit": true,
    "jsx": "react-jsx",
    /* Linting */
    "strict": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "noFallthroughCasesInSwitch": true,
    "baseUrl": ".",
    "paths": {
      "@/*": [
        "./src/*"
      ]
    }
  },
  "include": [
    "src"
  ]
}
```

```json
// tsconfig.node.json
{
  "compilerOptions": {
    "target": "ES2022",
    "lib": [
      "ES2023"
    ],
    "module": "ESNext",
    "skipLibCheck": true,
    /* Bundler mode */
    "moduleResolution": "bundler",
    "allowImportingTsExtensions": true,
    "isolatedModules": true,
    "moduleDetection": "force",
    "noEmit": true,
    /* Linting */
    "strict": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "noFallthroughCasesInSwitch": true,
    "baseUrl": ".",
    "paths": {
      "@/*": [
        "./src/*"
      ]
    }
  },
  "include": [
    "vite.config.ts"
  ]
}
```

and the shadcn init script is not respecting the `references` in the base `tsconfig.json`.

You can work around this by adding alias(es) to the base `tsconfig.json`, but this should not be required; not only is it redundant, it breaks LSP/autocomplete in neovim, and vite itself.

2. The `--path` option when trying to add a component (e.g. `npx shadcn@latest add button --path src/components/shadcn/ui` seems to be ignored regardless of the presence of aliases in `tsconfig.json`. 

I found this issue: https://github.com/shadcn-ui/ui/issues/1221 which describes the same problem, but it was closed due to inactivity.

### Affected component/components

CLI, all components

### How to reproduce

1. Follow the [vite install instructions](https://ui.shadcn.com/docs/installation/vite)
2. During creation of the vite project, choose typescript/react
3. Setup tailwindcss
4. Add alias(es) to `tsconfig.app.json` and `tsconfig.node.json`
5. Try to setup shadcn: `npx shadcn@latest init`; error: `No import alias found in your tsconfig.json file.` Workaround: add alias(es) to `tsconfig.json`

### Codesandbox/StackBlitz link

I didn't see a way to create a sandbox app with the vite+react+typescript template.

### Logs

_No response_

### System Info

```bash
Nothing special.


uname -a
Linux jezrien 6.10.5-zen1 #1-NixOS ZEN SMP PREEMPT_DYNAMIC Tue Jan  1 00:00:00 UTC 1980 x86_64 GNU/Linux
```
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues