Skip to content

Conversation

@ankrgyl
Copy link
Contributor

@ankrgyl ankrgyl commented Jan 2, 2026

No description provided.

@vercel
Copy link

vercel bot commented Jan 2, 2026

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

Project Deployment Review Updated (UTC)
ai-proxy Ready Ready Preview, Comment Jan 2, 2026 1:18am

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.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines 1 to 4
{
"compilerOptions": {
"baseUrl": ".",
"target": "es2015",
"lib": [

Choose a reason for hiding this comment

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

P1 Badge Reinstate baseUrl for path aliases

This tsconfig still declares paths mappings (e.g., @lib/*) but baseUrl was removed, and TypeScript requires baseUrl to be set whenever paths is present. Running tsc/Next build in apis/vercel will now fail with Option 'paths' cannot be used without specifying 'baseUrl', breaking alias resolution and the build.

Useful? React with 👍 / 👎.

Comment on lines 5 to 8
"target": "ES2018",
"strict": true,
"moduleResolution": "node",
"baseUrl": ".",
"paths": {

Choose a reason for hiding this comment

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

P1 Badge Keep baseUrl when using paths mappings

The proxy tsconfig retains paths entries but no longer sets baseUrl; TypeScript rejects paths without baseUrl, so tsc -p packages/proxy/tsconfig.json will now emit Option 'paths' cannot be used without specifying 'baseUrl' and fail to build, breaking the module aliases defined here.

Useful? React with 👍 / 👎.

When baseUrl is removed, TypeScript requires paths to start with ./
to be recognized as relative paths.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
After removing baseUrl, bare imports like `import from "utils"` need
explicit path aliases to resolve correctly.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@ankrgyl ankrgyl merged commit 682ec12 into main Jan 2, 2026
4 checks passed
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