Hi @pratham-radadiya thanks for working on this! I see you've marked a review comment resolved, do you plan to implement that suggestion in a future commit? In terms of scope: it looks like the top-level package and package-lock files were touched, could you confirm why this was necessary please?

Also tagging the other DevOps stewards on this one @Vaivaswat2244 @error-four-o-four @limzykenneth

I personally don't quite like the setup here introducing individual standalone project which adds a lot of complexity and the exec stuff can be very brittle as well.

I don't think there is a specific need to test React and Vue, the main thing from the original issue is looking at is around type correctness, React and Vue don't necessarily introduces different ways of working with types here. The original issue mention Vitest's type testing I think is a better direction. I would like our tests to remain within Vitest's ecosystem as much as possible so we don't build out toolings that are somewhat brittle and over time didn't get maintained and used, which is a problem we had with the 1.x devops setup.

Hi @ksen0 and @limzykenneth, thank you both for the detailed feedback!

On the package.json and package-lock.json changes:
These changes were required to include dependencies like vue-tsc, react, and typescript for the integration tests to run correctly in each ESM project. However, I understand now that this introduces unnecessary complexity at the top level. I’ll move these dependencies into local package.json files inside the test subfolders instead, or clean them up if we decide to drop Vue/React tests.

On the scope of React/Vue testing:
You're right — the original issue (#7938) was focused on verifying type correctness, and I see now that React/Vue may not bring extra value here. I can remove the React and Vue test setups and instead focus on tsc + Vitest’s type-only testing approach as suggested. That would keep things consistent with the existing testing strategy and avoid brittle tooling.

I'll push an updated commit shortly reflecting these changes. Please let me know if you'd like me to go in a slightly different direction — happy to adjust!