React types being pinned to 18.x to resolve version conflicts
Pinning @types/react and @types/react-dom to specific 18.x versions should eliminate the 100+ TypeScript errors caused by mixed type versions across the project.
The project was experiencing hundreds of TypeScript errors that were blocking developers from working effectively. The root cause was version mismatches in the React type definitions — @types/react and @types/react-dom were resolving to different versions, creating conflicts across the codebase.
Developers can now work without being blocked by type errors. The build environment is stabilized with pinned versions (18.2.69 for react types, 18.2.7 for react-dom types), ensuring consistency across all TypeScript compilations.
The fix is in the devDependencies of the root package.json.
View Original GitHub Description
I was getting 100s TypeScript errors across the project before this.