You are here |
alexsidorenko.com | ||
| | | |
hswolff.com
|
|
| | | | React Hooks! Hooks! Hooks! Hooks!Sorry, had to yell that a few times to get it out of my system.I definitely find React Hooks to be one of the most exciting new features that has hit React in a long time. I dont think Ive been this excited about a new feature since React Fragments and that was way | |
| | | |
tkdodo.eu
|
|
| | | | Let's demystify what stale closures are in combination with react hooks with the help of the analogy of taking a photo ... | |
| | | |
www.rasikjain.com
|
|
| | | | Introduction: React, being a popular JavaScript library for building user interfaces, provides various tools and features to handle state management. One such feature is useContext, which allows developers to share state across different components without prop drilling. In this blog post, we will explore the useContext feature in React and demonstrate its usage with a TypeScript example. Understanding useContext: The useContext hook is part of the React library and allows components to consume values fr... | |
| | | |
reactkungfu.com
|
|
| | Photo available thanks to the courtesy of seeminglee. CC BY-SA 2.0 There are three different ways to define your React components. With v0.13 version of React, the dev team took a great effort to enable using pure JavaScript classes available in the new ECMAScript 2015 standard. Using such classes allow you to write more idiomatic JavaScript. It also introduces less magic than the old React.createClass syntax. Each of these approaches have the slight differences and consequences when using them. In this blogpost I want to show you examples of component classes written using React.createClass, pure ECMAScript 2015 classes and ECMAScript 2015 classes with the experimental class properties feature. This will allow you to choose wisely between those three depending on your project needs. |