fix: TypeScript configuration files

[pzzyf]

Update TypeScript configuration to streamline type definitions and remove unnecessary options.

Summary by CodeRabbit

• Chores
  • Updated TypeScript configuration settings for improved project setup and type management. No changes to user-facing features.

[changeset-bot]

⚠️ No Changeset found

Latest commit: fa15038

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The changes update TypeScript configuration files for internal projects. In internal/tsconfig/node.json, the "composite" and "noImplicitAny" compiler options are removed, simplifying the configuration. In internal/tsconfig/web-app.json, the "vite/client" type is removed from the types array, narrowing the included type definitions to only "@vben/types/global". No changes to exported or public entities are present.

Changes

File(s)	Change Summary
internal/tsconfig/node.json	Removed "composite": false and "noImplicitAny": true from compiler options.
internal/tsconfig/web-app.json	Removed "vite/client" from types array, leaving only "@vben/types/global".

Suggested reviewers

• mynetfan

Poem

A nibble here, a tweak or two,
TypeScript configs, fresh and new!
Out goes "composite," "noImplicitAny" too,
Vite's client types bid adieu.
Now the code is neat and bright,
Ready for a bunny's hop to new delight! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 17a18fc and cd5efa4.

📒 Files selected for processing (2)

• internal/tsconfig/node.json (1 hunks)
• internal/tsconfig/web-app.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (8)

• GitHub Check: post-update (ubuntu-latest)
• GitHub Check: Check (windows-latest)
• GitHub Check: post-update (windows-latest)
• GitHub Check: Check (ubuntu-latest)
• GitHub Check: Test (windows-latest)
• GitHub Check: Lint (windows-latest)
• GitHub Check: Lint (ubuntu-latest)
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (2)

internal/tsconfig/web-app.json (1)

6-6: Verify removal of Vite client types won’t break build or IDE support.
The "vite/client" entry provided typings for import.meta.env and other Vite-specific globals. Confirm that these globals are either no longer used or are declared elsewhere (e.g., in a custom declaration file). Run a dev‐mode compile and spot-check that features like import.meta.env still have proper typings.

internal/tsconfig/node.json (1)

8-8: Check for redundancy or missing types in Node config.
You’ve explicitly added "types": ["node"] here—verify that ./base.json doesn’t already include this setting (to avoid duplication). Also ensure that removing strict flags (composite, noImplicitAny) hasn’t inadvertently weakened type safety in your Node projects.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.