Skip to content

Update tsconfig.json #16703

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Update tsconfig.json #16703

wants to merge 3 commits into from

Conversation

dannyroosevelt
Copy link
Collaborator

@dannyroosevelt dannyroosevelt commented May 16, 2025

WHY

Summary by CodeRabbit

  • Chores
    • Improved build process with enhanced logging and path resolution for better development reliability. No changes affecting user experience.

Copy link

vercel bot commented May 16, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

3 Skipped Deployments
Name Status Preview Comments Updated (UTC)
docs-v2 ⬜️ Ignored (Inspect) Visit Preview May 16, 2025 10:14pm
pipedream-docs ⬜️ Ignored (Inspect) May 16, 2025 10:14pm
pipedream-docs-redirect-do-not-edit ⬜️ Ignored (Inspect) May 16, 2025 10:14pm

Copy link
Contributor

coderabbitai bot commented May 16, 2025

Walkthrough

The build process for the @pipedream/ai package was updated to run tsc-alias after the TypeScript compiler (tsc), even if tsc fails, by modifying the build script and adding tsc-alias as a devDependency. The tsconfig.json was also updated to include a tsc-alias configuration enabling verbose logging and full path resolution.

Changes

File(s) Change Summary
packages/ai/tsconfig.json Added a tsc-alias section with "verbose": true and "resolveFullPaths": true options.
packages/ai/package.json Modified build script to run tsc-alias after tsc regardless of tsc success; added tsc-alias as a devDependency.

Poem

A tweak to the config, quiet as a hare,
Now paths resolve fully, with verbose flair.
The build script hops, runs two steps in line,
tsc then tsc-alias, no errors confine.
The AI package grows, with paths clear and bright,
A rabbit’s small dance in the code’s soft light.
🐇✨

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
packages/ai/tsconfig.json (1)

15-18: Ensure tsc-alias is wired into your build pipeline
You’ve added the tsc-alias configuration correctly, but this block will be ignored unless:

  1. tsc-alias is installed in devDependencies.
  2. Your build (or postbuild) script invokes tsc-alias after tsc.

Please verify that packages/ai/package.json has something like:

"devDependencies": {
  "tsc-alias": "^1.8.0"
},
"scripts": {
  "build": "tsc && tsc-alias"
}
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between a9b1757 and b164cf3.

📒 Files selected for processing (1)
  • packages/ai/tsconfig.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: pnpm publish
  • GitHub Check: Lint Code Base

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between b164cf3 and f528f52.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (1)
  • packages/ai/package.json (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Lint Code Base
🔇 Additional comments (2)
packages/ai/package.json (2)

31-32: Confirm and document new devDependency openai
The PR adds both openai and tsc-alias under devDependencies. While tsc-alias is correctly categorized, please clarify in the PR description:

  1. Why openai was added.
  2. If openai is required at runtime, move it to dependencies so it’s installed in production.

Likely an incorrect or invalid review comment.


32-32: Approve addition of tsc-alias devDependency
Aligns with the updated tsconfig.json alias configuration and ensures path imports are correctly rewritten after compilation.

@@ -19,7 +19,7 @@
"access": "public"
},
"scripts": {
"build": "tsc"
"build": "tsc || echo 'tsc failed, continuing anyway' && tsc-alias"
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Raise critical concern: suppressing TypeScript errors masks build failures
By using tsc || echo 'tsc failed, continuing anyway' && tsc-alias, all type-checking errors are hidden, potentially leading to shipping broken code. If the goal is to always run tsc-alias, consider:

  • Splitting into "build": "tsc && npm run postbuild" and "postbuild": "tsc-alias" to preserve failure on errors.
  • Or adjusting tsconfig.json (e.g., disabling noEmitOnError) instead of ignoring all tsc failures.
🤖 Prompt for AI Agents
In packages/ai/package.json at line 22, the build script suppresses TypeScript
errors by using 'tsc || echo ... && tsc-alias', which hides build failures. To
fix this, split the build script into two separate scripts: set "build" to run
'tsc' and then, only if successful, run a new "postbuild" script that executes
'tsc-alias'. This preserves error detection while ensuring tsc-alias runs after
a successful build. Alternatively, adjust tsconfig.json to disable
'noEmitOnError' if you want to allow emitting despite errors without suppressing
them in the script.

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.

1 participant