Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
React and React Native

You're reading from   React and React Native Build cross-platform JavaScript apps with native power for mobile, web and desktop

Arrow left icon
Product type Paperback
Published in Mar 2017
Publisher Packt
ISBN-13 9781786465658
Length 500 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Adam Boduch Adam Boduch
Author Profile Icon Adam Boduch
Adam Boduch
Arrow right icon
View More author details
Toc

Table of Contents (27) Chapters Close

Preface 1. Why React? FREE CHAPTER 2. Rendering with JSX 3. Understanding Properties and State 4. Event Handling – The React Way 5. Crafting Reusable Components 6. The React Component Lifecycle 7. Validating Component Properties 8. Extending Components 9. Handling Navigation with Routes 10. Server-Side React Components 11. Mobile-First React Components 12. Why React Native? 13. Kickstarting React Native Projects 14. Building Responsive Layouts with Flexbox 15. Navigating Between Screens 16. Rendering Item Lists 17. Showing Progress 18. Geolocation and Maps 19. Collecting User Input 20. Alerts, Notifications, and Confirmation 21. Responding to User Gestures 22. Controlling Image Display 23. Going Offline 24. Handling Application State 25. Why Relay and GraphQL? 26. Building a Relay React App

Frontend reconciliation

The only thing that was missing from the last example was the client JavaScript code. No big deal, right? The user actually wants to use the application and the server needs to deliver the client code bundle. How would this work? We want routing to work in both the frontend and the backend, without modification to the routes themselves. In other words, the server handles routing in the initial request, then the browser takes over as the user starts clicking things and moving around in the application.

This is pretty easy to do. Let's create a main module (it probably looks familiar from examples in the previous chapter):

import React from 'react'; 
import { render } from 'react-dom'; 
 
import routes from './routes'; 
 
// Nothing special here. React sees the checksum on the 
// root element, and determines that there's no need 
// to render data yet. 
render( 
  routes, 
  document.getElementById('app') 
); 

That&apos...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at AU $24.99/month. Cancel anytime