2022-04-21
1109
#react#typescript
John Reilly
105029
Apr 21, 2022 ⋅ 3 min read

Upgrading to React 18 with TypeScript

John Reilly MacGyver turned Dev 🌻❤️ TypeScript / ts-loader / fork-ts-checker-webpack-plugin / DefinitelyTyped: The Movie

Recent posts:

DesignCoder and the future of AI-generated UI

From sketches to code in minutes, DesignCoder shows how AI-generated, hierarchy-aware UIs could change the way developers prototype and ship apps.

Rosario De Chiara
Oct 7, 2025 ⋅ 5 min read

Would You Use If() functions in CSS?

It’s 2025, and CSS finally thinks logically. The if() function brings real conditional styling — no hacks, no JS workarounds. Here’s how to use it right.

Ikeh Akinyemi
Oct 7, 2025 ⋅ 16 min read
Typescript or Zod for Validation?

TypeScript vs Zod: Clearing up validation confusion

Learn when to use TypeScript, Zod, or both for data validation. Avoid redundant checks and build safer, type-sound applications.

Alexander Godwin
Oct 6, 2025 ⋅ 3 min read
Wasm 3 Before GTA 6 LogRocket Article

We got Wasm 3.0 before GTA 6: Meet the web’s new engine

Discover how WebAssembly 3.0’s garbage collector, exception handling, and Memory64 transform Wasm into a true mainstream web platform.

Ikeh Akinyemi
Oct 3, 2025 ⋅ 2 min read
View all posts

2 Replies to "Upgrading to React 18 with TypeScript"

  1. The main change required to make this work in React 18 is missing in the blog. For instance, if you do not use the new createRoot API to initiate the application the react application reverts back to version 17 which is essentially wrong as the main intention to do this update is to use react 18 and the new features it has under the hood.

    The following link from React seems to be a better way of upgrade as they have also removed unmountcomponentatnode() method as well: https://reactjs.org/blog/2022/03/08/react-18-upgrade-guide.html

Leave a Reply