Building a Better Web
June 19–20, 2017: Training
June 20–22, 2017: Tutorials & Conference
San Jose, CA

Deep dive into the React component lifecycle

Jonathan Creamer (Lonely Planet)
9:00am–9:40am Thursday, June 22, 2017
Secondary topics:  JavaScript frameworks and libraries (Angular, React, Ember, Vue, etc.), JavaScript/ES6
Average rating: ****.
(4.29, 7 ratings)

Who is this presentation for?

  • JavaScript engineers

Prerequisite knowledge

  • An understanding of basic React concepts

What you'll learn

  • Understand how to use the React lifecycle to build smart components

Description

As a beginner, heck even as a veteran, trying to understand all of the different lifecycle events in a React component can be a bit daunting. You’ll often find yourself googling which one to use even after spending months working with React because each method has different uses. There are times when you need to know when a component has loaded to add some kind of JavaScript plugin or know when a component’s props have changed, for example. Knowing how and when to use each of these methods can make building applications much easier. Jonathan Creamer goes through each lifecycle method, giving some examples of how and when to use them.

Photo of Jonathan Creamer

Jonathan Creamer

Lonely Planet

Jonathan Creamer is a Senior Engineer at Lonely Planet. Jonathan is active in the development community and frequently attends user groups like NashJS, NashReact, and NashDotNet. He also blogs for Jonathan Creamer.com, Net Tuts, Smashing
Magazine—when he’s not scouring Twitter and the internet for as much knowledge as he can squeeze into his brain. Jonathan is a Microsoft MVP. He loves meeting other devs who are passionate about what they do.

Comments on this page are now closed.

Comments

Picture of Jonathan Creamer
Jonathan Creamer | JAVASCRIPT ENGINEER
06/28/2017 5:40am PDT

Slides link should be fixed now. Thanks!

David Ferreira | TECHNICAL LEAD DEVELOPER
06/28/2017 5:24am PDT

Hello, looks like the view slides link is broken. “This site can’t be reached”