Ben Ilegbodu

Have you ever gotten this warning while developing React components?

Have you ever run into a problem where TypeScript incorrectly infers the types of properties of an object?

I try to be as strict as possible when I use TypeScript.

Happy 2021!

Hooks launched in React with [v16.8](https://reactjs.org/blog/2019/02/06/react-v16.8.0.html) nearly 2 years ago, enabling us to use state and other React features without writing a class.

One of my favorite sayings about React is that it's "Just JavaScript™."

The biggest benefit I've found with TypeScript is type-checking functions.

Two weeks ago I wrote about [Conditional React prop types with TypeScript](/blog/conditional-react-props-typescript/).

Last week I wrote a post about [conditional React prop types with TypeScript](/blog/conditional-react-props-typescript/) that generated a lot of [discussion on Twitter](https://twitter.com/benmvp/status/1323415760220299264).

The [`useEffect` hook](https://reactjs.org/docs/hooks-reference.html#useeffect) in React by default runs on every re-render: ```js {4-6} const Example = () => { const [count, setCount] = useState(0) useEffect(() => { document.title = `You clicked ${count}…

So… yeah the title is kinda clickbait-y, but it’s kinda true.

A few months ago I wrote a post called [What exactly is a "Design System"?]

Back in April I wrote a blog post about how I would [choose React Testing Library over Enzyme](/blog/react-testing-library-over-enzyme/).

As a new bootcamp or college graduate, your first job can be really critical in determining the trajectory of your career.

If you haven't realized yet, I enjoy teaching.

Like clockwork the [_Learning ES6_ series](/learning-es6-series/) continues on, looking at _promises_.