Skip to content

Conversation

@DocPis
Copy link
Owner

@DocPis DocPis commented Jan 12, 2026

a

@vercel
Copy link

vercel bot commented Jan 12, 2026

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

Project Deployment Review Updated (UTC)
currentx-dex Ready Ready Preview, Comment Jan 13, 2026 9:27pm
currentx-landing Ready Ready Preview, Comment Jan 13, 2026 9:27pm

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: deba034ba1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +3 to +5
{ "src": "/", "dest": "/landing.html" },
{ "handle": "filesystem" },
{ "src": "/.*", "dest": "/index.html" }
{ "src": "/.*", "dest": "/landing.html" }

Choose a reason for hiding this comment

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

P1 Badge Ensure landing.html is emitted in the Vite build

Because the routes now rewrite all requests to /landing.html, production will depend on that file being present in the build output. The current Vite config only builds index.html (no build.rollupOptions.input for landing.html), so landing.html will not be emitted into dist and the rewrite will 404 in production unless you add it as an input or move it under public/. This breaks the landing deploy whenever the Vercel build uses Vite’s default config.

Useful? React with 👍 / 👎.

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