-
Notifications
You must be signed in to change notification settings - Fork 61
remove baseUrl from tsconfig #368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this 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".
| { | ||
| "compilerOptions": { | ||
| "baseUrl": ".", | ||
| "target": "es2015", | ||
| "lib": [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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 👍 / 👎.
| "target": "ES2018", | ||
| "strict": true, | ||
| "moduleResolution": "node", | ||
| "baseUrl": ".", | ||
| "paths": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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>
No description provided.