pnpm dlx ai-elements-vue@latest fails: registry item Card.vue.json missing name/type

[imohuan]

Describe the bug
Running pnpm dlx ai-elements-vue@latest immediately aborts while “Checking registry” because it cannot parse https://registry.ai-elements-vue.com/Card.vue.json. The registry response lacks the required name and type fields, so the installer exits with error.

Command / Log

PS F:\Code\ai-elements-vue> pnpm dlx ai-elements-vue@latest
⠏ Checking registry.
Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

Error:
Failed to parse registry item: https://registry.ai-elements-vue.com/Card.vue.json
  - name: Required
  - type: Required

Message:
[
  {
    "code": "invalid_type",
    "expected": "string",
    "received": "undefined",
    "path": [
      "name"
    ],
    "message": "Required"
  },
  {
    "expected": "'registry:lib' | 'registry:block' | 'registry:component' | 'registry:ui' | 'registry:hook' | 'registry:composable' | 'registry:page' | 'registry:file' | 'registry:theme' | 'registry:style' | 'registry:item' | 'registry:example' | 'registry:internal'",
    "received": "undefined",
    "code": "invalid_type",
    "path": [
      "type"
    ],
    "message": "Required"
  }
]

Suggestion:
The registry item may be corrupted or have an invalid format. Please make sure it returns a valid JSON object. See https://shadcn-vue.com/schema/registry-item.json.
Command failed with exit code 1

Steps to reproduce

1. Open PowerShell on Windows 10 (build 19045)
2. Navigate to any folder (e.g. F:\Code\ai-elements-vue)
3. Run pnpm dlx ai-elements-vue@latest
4. Observe the failure during the registry check.

Expected behavior
The CLI should fetch a valid registry entry for Card.vue (with name and type populated) and continue installing.

Actual behavior
Registry parsing fails because the response lacks name and type, so the CLI exits with status 1.

Environment

• OS: Windows 10 (10.0.19045)
• Shell: PowerShell 5.1
• pnpm: (your version here, e.g. 9.x)
• Node: (your version here)

Additional context
Happens consistently; likely the registry item is malformed or returning a non-JSON response. Let me know if you need any additional diagnostics.