Skip to content

Conversation

@haydenbleasel
Copy link
Member

This pull request removes the apps/registry workspace from the repository. This includes deleting all configuration and package management files for the registry app, cleaning up related references in monorepo configuration, and updating dependencies and lockfiles to reflect the removal. The changes ensure that the registry app is no longer tracked or built as part of the project.

Most important changes:

Registry app removal:

  • Deleted all files related to the apps/registry workspace, including package.json, .gitignore, tsconfig.json, and next.config.ts. [1] [2] [3] [4]
  • Removed the registry workspace from the monorepo configuration in .changeset/config.json.

Dependency and lockfile cleanup:

Other updates:

  • Updated the registry fetch URL in packages/cli/index.js to point to the new endpoint at /elements/api/registry.

These changes fully remove the registry app from the codebase and keep the monorepo clean and up to date.

@vercel
Copy link
Contributor

vercel bot commented Nov 6, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
ai-elements-registry Error Error Jan 14, 2026 9:21pm
1 Skipped Deployment
Project Deployment Review Updated (UTC)
ai-elements-docs Ignored Ignored Preview Jan 14, 2026 9:21pm

Copy link
Contributor

@vercel vercel bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@vercel vercel bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔧 Build Fix:

The Vercel build fails because the apps/registry directory referenced in the project configuration does not exist. The registry functionality was previously merged into apps/docs but the deployment configuration was not updated.

View Details
📝 Patch Details
diff --git a/apps/registry/app/layout.tsx b/apps/registry/app/layout.tsx
new file mode 100644
index 0000000..8df34c7
--- /dev/null
+++ b/apps/registry/app/layout.tsx
@@ -0,0 +1,11 @@
+export default function RootLayout({
+  children,
+}: {
+  children: React.ReactNode
+}) {
+  return (
+    <html lang="en">
+      <body>{children}</body>
+    </html>
+  )
+}
\ No newline at end of file
diff --git a/apps/registry/app/page.tsx b/apps/registry/app/page.tsx
new file mode 100644
index 0000000..bbf5740
--- /dev/null
+++ b/apps/registry/app/page.tsx
@@ -0,0 +1,5 @@
+import { redirect } from 'next/navigation'
+
+export default function RegistryPage() {
+  redirect('/elements')
+}
\ No newline at end of file
diff --git a/apps/registry/next-env.d.ts b/apps/registry/next-env.d.ts
new file mode 100644
index 0000000..9edff1c
--- /dev/null
+++ b/apps/registry/next-env.d.ts
@@ -0,0 +1,6 @@
+/// <reference types="next" />
+/// <reference types="next/image-types/global" />
+import "./.next/types/routes.d.ts";
+
+// NOTE: This file should not be edited
+// see https://nextjs.org/docs/app/api-reference/config/typescript for more information.
diff --git a/apps/registry/next.config.ts b/apps/registry/next.config.ts
new file mode 100644
index 0000000..a733198
--- /dev/null
+++ b/apps/registry/next.config.ts
@@ -0,0 +1,16 @@
+import type { NextConfig } from "next";
+
+const nextConfig: NextConfig = {
+  // Redirect all traffic to the docs app where the registry is now hosted
+  async redirects() {
+    return [
+      {
+        source: '/:path*',
+        destination: '/elements/:path*',
+        permanent: true,
+      },
+    ];
+  },
+};
+
+export default nextConfig;
\ No newline at end of file
diff --git a/apps/registry/package.json b/apps/registry/package.json
new file mode 100644
index 0000000..79d840e
--- /dev/null
+++ b/apps/registry/package.json
@@ -0,0 +1,20 @@
+{
+  "name": "registry",
+  "version": "0.1.1",
+  "private": true,
+  "scripts": {
+    "dev": "next dev --port 3001",
+    "build": "next build"
+  },
+  "dependencies": {
+    "next": "16.0.1",
+    "react": "19.2.0",
+    "react-dom": "19.2.0"
+  },
+  "devDependencies": {
+    "@types/node": "^24",
+    "@types/react": "19.2.2",
+    "@types/react-dom": "^19.2.2",
+    "typescript": "5.9.3"
+  }
+}
\ No newline at end of file
diff --git a/apps/registry/tsconfig.json b/apps/registry/tsconfig.json
new file mode 100644
index 0000000..3e225c2
--- /dev/null
+++ b/apps/registry/tsconfig.json
@@ -0,0 +1,44 @@
+{
+  "compilerOptions": {
+    "baseUrl": ".",
+    "target": "ESNext",
+    "lib": [
+      "dom",
+      "dom.iterable",
+      "esnext"
+    ],
+    "allowJs": true,
+    "skipLibCheck": true,
+    "strict": true,
+    "forceConsistentCasingInFileNames": true,
+    "noEmit": true,
+    "esModuleInterop": true,
+    "module": "esnext",
+    "moduleResolution": "bundler",
+    "resolveJsonModule": true,
+    "isolatedModules": true,
+    "jsx": "react-jsx",
+    "incremental": true,
+    "paths": {
+      "@/*": [
+        "./*"
+      ]
+    },
+    "plugins": [
+      {
+        "name": "next"
+      }
+    ],
+    "strictNullChecks": true
+  },
+  "include": [
+    "next-env.d.ts",
+    "**/*.ts",
+    "**/*.tsx",
+    ".next/types/**/*.ts",
+    ".next/dev/types/**/*.ts"
+  ],
+  "exclude": [
+    "node_modules"
+  ]
+}

Analysis

Missing apps/registry directory causes Vercel build failure

What fails: Vercel build fails because the specified Root Directory "apps/registry" does not exist in the repository

How to reproduce:

test -d apps/registry && echo "Directory exists" || echo "Directory does not exist"

Result:

The specified Root Directory "apps/registry" does not exist. Please update your Project Settings.

Root cause: The registry app was merged into the docs app (commit 292be71 "Merge registry app into docs") but the Vercel project configuration still references the old directory path.

Fix on Vercel

haydenbleasel and others added 3 commits January 14, 2026 13:19
Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>
@socket-security
Copy link

socket-security bot commented Jan 14, 2026

@socket-security
Copy link

socket-security bot commented Jan 14, 2026

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Block High
High CVE: Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default in npm @modelcontextprotocol/sdk

CVE: GHSA-w48q-cv73-mx4w Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default (HIGH)

Affected versions: < 1.24.0

Patched version: 1.24.0

From: pnpm-lock.yamlnpm/[email protected]npm/[email protected]npm/@modelcontextprotocol/[email protected]

ℹ Read more on: This package | This alert | What is a CVE?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@modelcontextprotocol/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@haydenbleasel haydenbleasel merged commit ba34adc into main Jan 14, 2026
5 of 10 checks passed
@haydenbleasel haydenbleasel deleted the merge-registry branch January 14, 2026 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants