Skip to content

Conversation

@mattKorwel
Copy link
Collaborator

reverting changes to tsconfig.json

@mattKorwel mattKorwel requested a review from a team as a code owner October 27, 2025 21:35
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @mattKorwel, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses an issue where the TypeScript build process for the core package was not idempotent. It resolves this by reverting a previous change to the tsconfig.json file, specifically by removing the inclusion of declaration files (src/**/*.d.ts) from the build scope. This ensures consistent build outputs and prevents potential build-related side effects.

Highlights

  • TypeScript Configuration Reversion: The primary change involves reverting a previous modification to the tsconfig.json file located in the packages/core directory.
  • Idempotent Build Fix: The src/**/*.d.ts pattern has been removed from the include array within tsconfig.json. This adjustment aims to ensure that the tsc build process for the package/core is idempotent, preventing inconsistent build outputs.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request reverts a change in packages/core/tsconfig.json to fix a CI build idempotency issue by removing src/**/*.d.ts from the include array. While this likely resolves the immediate problem, I have added a review comment highlighting the potential risk of this change unintentionally excluding necessary ambient type declarations. I've also suggested a more robust, long-term architectural solution to handle such declaration files.

"types": ["node", "vitest/globals"]
},
"include": ["index.ts", "src/**/*.ts", "src/**/*.d.ts", "src/**/*.json"],
"include": ["index.ts", "src/**/*.ts", "src/**/*.json"],
Copy link
Contributor

Choose a reason for hiding this comment

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

high

Removing src/**/*.d.ts from include may cause build failures if any manually-created ambient declaration files exist within the src directory. TypeScript will no longer automatically include these files, which can break type resolution for global augmentations or modules that are not explicitly imported (e.g., for assets like CSS/images or untyped dependencies), resulting in errors like TS2307: Cannot find module '...'.

While this change likely fixes the idempotency issue, a more robust long-term solution is to isolate necessary ambient declarations. Consider moving any such .d.ts files to a dedicated top-level types directory and including it via the typeRoots compiler option. This makes their global nature explicit and avoids potential conflicts with source files.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@cornmander this is likely relevant to the changes you were tryign to make originally in #11157

Copy link
Collaborator

Choose a reason for hiding this comment

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

I think it's fine, the tsignore at

// @ts-ignore resolved by esbuild-plugin-wasm during bundling
makes this work even w/o the type file.

@github-actions
Copy link

Size Change: -2 B (0%)

Total Size: 20.2 MB

ℹ️ View Unchanged
Filename Size Change
./bundle/gemini.js 20.2 MB -2 B (0%)
./bundle/sandbox-macos-permissive-closed.sb 1.03 kB 0 B
./bundle/sandbox-macos-permissive-open.sb 890 B 0 B
./bundle/sandbox-macos-permissive-proxied.sb 1.31 kB 0 B
./bundle/sandbox-macos-restrictive-closed.sb 3.29 kB 0 B
./bundle/sandbox-macos-restrictive-open.sb 3.36 kB 0 B
./bundle/sandbox-macos-restrictive-proxied.sb 3.56 kB 0 B

compressed-size-action

@mattKorwel mattKorwel merged commit cb0947c into main Oct 27, 2025
20 checks passed
@mattKorwel mattKorwel deleted the tsc-fix branch October 27, 2025 21:39
thacio added a commit to thacio/auditaria that referenced this pull request Oct 29, 2025
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