Exciting news!Announcing our $4.6M Series Seed. Learn more
Socket
LoveBlogFAQ
Install
Log in

react-lazy-data

Package Overview
Dependencies
8
Maintainers
1
Versions
11
Issues
File Explorer

Advanced tools

react-lazy-data

Lazy-load data with React Suspense

    0.2.4latest

Version published
Maintainers
1
Yearly downloads
11,699
increased by206.5%

Weekly downloads

Changelog

Source

0.2.4

Build:

  • Remove __DEV__ from builds [fix]

Readme

Source

NPM version Build Status Dependency Status Dev dependency Status Greenkeeper badge Coverage Status

Lazy-load data with React Suspense

What's it for?

React does not officially support using Suspense for data fetching. This package makes that possible.

It also supports server-side rendering using react-async-ssr.

NB Does not require experimental builds of React, or "concurrent mode". Tested and working on all versions of React 16.8.0+.

React 16.8.x or 16.9.x (and not higher) is recommended for server-side rendering.

Usage

There are two APIs:

  1. Event-based
  2. Hooks

The moving parts

Resource Factory

A Resource Factory defines the method for fetching data.

You call the Factory's .create() or .use() method to initiate fetching data and create a Resource.

import { createResourceFactory } from 'react-lazy-data'; // Create Resource Factory const PokemonResource = createResourceFactory( id => fetch(`https://pokeapi.co/api/v2/pokemon/${id}`) .then(res => res.json()) ); // Create Resource const pokemonResource = PokemonResource.create( 1 );

Resource

A Resource represents data being fetched. It can be pending, complete, or errored - much like a Promise.

Resources have a .read() method which a component can call to get the underlying data.

If the data is loaded, .read() returns the data. If the data is not ready yet, .read() throws a Promise which bails out of rendering the component and "suspends" the Suspense boundary above it. When the data is loaded, the Promise resolves which causes React to re-render the component. .read() will then return the data. If data-loading fails, .read() will throw the error that the fetch promise rejected with.

This may sound odd, but it's how Suspense works. React.lazy() works the same way - if the lazy component is not loaded yet, it throws a Promise which resolves when it is loaded.

So you can write a component that uses async data in a synchronous style:

function Pokemon( { pokemonResource } ) { // Read the resource const pokemon = pokemonResource.read(); // This will only run once the data is ready return <div>My name is {pokemon.name}.</div>; }

Event-based API

This is the approach recommended by React - load data in event handlers.

import { createResourceFactory } from 'react-lazy-data'; const PokemonResource = createResourceFactory( id => fetch(`https://pokeapi.co/api/v2/pokemon/${id}`) .then(res => res.json()) ); function App() { const [id, setId] = useState( 1 ); const resourceRef = useRef(); const resource = resourceRef.current || createResource( id ); function createResource( id ) { const resource = PokemonResource.create( id ); resourceRef.current = resource; return resource; } const next = useCallback( () => { const previousResource = resourceRef.current; if ( previousResource ) previousResource.dispose(); setId( id => { const newId = id + 1; createResource( newId ); return newId; } ); }, [] ); return ( <div> <Suspense fallback={ <div>Loading...</div> }> <Pokemon resource={ resource } /> </Suspense> <button onClick={ next }>Next Pokemon!</button> </div> ); } function Pokemon( { resource } ) { const pokemon = resource.read(); return <div>My name is {pokemon.name}.</div>; }

As you can see, it's not very ergonomic. You have to manually take care of disposing of the old resource when you're done with it, in the event handler.

Hooks API

(requires React 16.8.0+)

import { createResourceFactory } from 'react-lazy-data'; const PokemonResource = createResourceFactory( id => fetch(`https://pokeapi.co/api/v2/pokemon/${id}`) .then(res => res.json()) ); function App() { const [id, setId] = useState( 1 ); const resource = PokemonResource.use( id ); return ( <div> <Suspense fallback={ <div>Loading...</div> }> <Pokemon resource={ resource } /> </Suspense> <button onClick={ () => setId( id => id + 1 ) }>Next Pokemon!</button> </div> ); } function Pokemon( { resource } ) { const pokemon = resource.read(); return <div>My name is {pokemon.name}.</div>; }

.use() is a React hook.

The hooks-based API takes care of disposing old resources automatically.

Whenever the argument passed to .use() changes, it disposes the old resource and creates a new one, triggering loading the new data. If the component which called .use() is unmounted, the resource is disposed.

Note that the Pokemon component is exactly the same with either the event-based or hooks-based APIs. The difference is in how the Resource is created, not how it's used.

IMPORTANT: The one rule

Due to how React works, you must not call .use() and .read() in the same component. One component must create the resource with .use(), and then pass the resource to a 2nd component to render it.

// DON'T DO THIS - IT WON'T WORK function Pokemon( { id } ) { const resource = PokemonResource.use( id ); const pokemon = resource.read(); return <div>My name is {pokemon.name}.</div>; } // This works function Pokemon( { id } ) { const resource = PokemonResource.use( id ); return <PokemonDisplay resource={ resource } />; } function PokemonDisplay( { resource } ) { const pokemon = resource.read(); return <div>My name is {pokemon.name}.</div>; }

You can use withResources() to remove some of the boilerplate code.

Wait a second! You're not meant to perform effects in the render phase.

Quite right!

It looks like .use() is doing this, but actually it's not. Internally, .use() performs the data loading inside a useEffect() hook. This is what allows it to automatically dispose of defunct resources.

Aborting data fetching

If you are changing the data you load frequently, you may want to abort fetch requests in flight if their results are no longer required.

If the promise returned by the fetch function has an .abort() method, it will be called when the resource is disposed.

e.g. Using fetch() and AbortController:

function abortableFetchJson( url ) { const abortController = new AbortController(); const promise = fetch( url, { signal: abortController.signal } ).then( res => res.json() ); promise.abort = () => abortController.abort(); return promise; } // Create Resource Factory const PokemonResource = createResourceFactory( id => abortableFetchJson(`https://pokeapi.co/api/v2/pokemon/${id}`) ); // Create resource - fetching begins const resource = PokemonResource.create( 1 ); // Dispose resource - fetch request is aborted resource.dispose();

NB .dispose() does not call the Promise's .abort() method if the Promise has already resolved.

If you're using the hooks-based API, .use() takes care of disposal for you. All you need to do is make sure the promises returned by the createResourceFactory() fetch function have an .abort() method.

const PokemonResource = createResourceFactory( id => abortableFetchJson(`https://pokeapi.co/api/v2/pokemon/${id}`) ); function App() { const [id, setId] = useState( 1 ); const resource = PokemonResource.use( id ); return ( <div> <Suspense fallback={ <div>Loading...</div> }> <Pokemon resource={ resource } /> </Suspense> <button onClick={ () => setId( id => id + 1 ) }>Next Pokemon!</button> </div> ); } function Pokemon( { resource } ) { const pokemon = resource.read(); return <div>My name is {pokemon.name}.</div>; }

If you click "Next Pokemon!" before the previous data has finished loading, the old fetch is aborted before the next fetch commences. So you're not using bandwidth for data which won't be used.

NB The only thing which has changed from previous .use() example is in the fetch function passed to createResourceFactory(). Everything else is unchanged.

Caching

If two components may both require the same data concurrently, and call .create() or .use() with the same argument, you can ensure the fetch is only performed once - to save bandwidth and ensure data consistency.

To enable caching, pass a serialize option to createResourceFactory().

serialize should be a function which serializes the request argument to a string, which will act as the cache key. serialize: true will use the default serializer, JSON.stringify.

If .create() or .use() is called again with an argument which serializes to the same cache key, the resource which is returned from the 2nd call "follows" the original, rather than fetching again.

The cache lives only as long as active resources which are using it. Once all resources relating to a particular request are disposed, the cache is cleared. So a later call to .create() or .use() will fetch again, and get fresh data.

const Resource = createResourceFactory( id => fetch(`https://pokeapi.co/api/v2/pokemon/${id}`).then(res => res.json()), { serialize: true } ); const resource1 = Resource.create( 1 ); // `fetch()` is called const resource2 = Resource.create( 1 ); // `fetch()` is not called again - cache ensures no repeat calls // Each resource is different, // so they can be disposed individually resource1 === resource2 // => false // ...time passes, fetch completes... // `.read()` returns same result on both resources resource1.read() // => { id: 1, ... } resource2.read() // => { id: 1, ... } // Further calls to `.create()` or `.use()` // return a resource pre-populated with cached result const resource3 = Resource.create( 1 ); resource3.read() // => { id: 1, ... } // Dispose all resources resource1.dispose(); resource2.dispose(); resource3.dispose(); // Cache is now cleared // Now fetch will be called again to get fresh data const resource4 = Resource.create( 1 ); // `fetch()` is called again

withResources()

To avoid having to call .read(), you can instead wrap components which use Resources in withResources().

When a wrapped component is rendered, it checks if any of its props are Resources. If they are, it calls .read() on the Resources before rendering the original component. So then you can just use the data directly, rather than having to call .read() yourself.

Same example as above, but using withResources():

import { withResources } from 'react-lazy-data'; const PokemonDisplay = withResources( ( { pokemon } ) => <div>My name is {pokemon.name}.</div> }; function Pokemon( { id } ) { const pokemonResource = PokemonResource.use( id ); return <PokemonDisplay pokemon={ pokemonResource } />; }

NB withResources() only does a shallow search of props for Resources. i.e. if props are { pokemon: resource }, the resource will be found and read. But if props are { myStuff: { pokemon: resource } }, it won't.

Usage with React.lazy()

withResources() should be used to wrap a component before it is wrapped with React.lazy().

// DON'T DO THIS // It will work, but it'll delay loading the Lazy component // until after data loads. const Pokemon = withResources( React.lazy( () => import( './Pokemon.js' ) ) ); // This works better - Lazy component and data load concurrently // App.js const Pokemon = React.lazy( () => import( './Pokemon.js' ) ); // Pokemon.js export default withResources( ( { pokemon } ) => <div>My name is {pokemon.name}.</div> );

isResource()

Utility function to determine if a value is a Resource.

import { isResource } from 'react-lazy-data'; const resource = PokemonResource.create( 1 ); isResource( resource ) // => `true` isResource( { foo: 'bar' } ) // => `false`

Server-side rendering

Server-side rendering is supported by this package when using react-async-ssr in place of React's native server rendering methods.

There are 3 elements to making server-side rendering work:

  1. Give each Resource Factory a unique ID
  2. Capture data loaded on server and transmit it to browser along with HTML
  3. Load the data cache in browser with server-loaded data before hydration

This package provides methods to do all 3 of these things.

NB Server-side rendering automatically enables caching.

1. Naming Resource Factories

All resource factories must be given an ID, using the id option. Every call to createResourceFactory() must provide an ID which must be unique within the whole application.

import { createResourceFactory } from 'react-lazy-data'; // Create Resource Factory const PokemonResource = createResourceFactory( id => fetch(`https://pokeapi.co/api/v2/pokemon/${id}`).then(res => res.json()), { id: 'pokemon' } );

Or to create unique IDs automatically, you can use a Babel plugin provided by this package:

// babel.config.json { "plugins": [ "react-lazy-data/babel" ] }

The Babel plugin will add a unique ID to every call to createResourceFactory(). The IDs are a hash of the file's path relative to the application's root and a counter. IDs are deterministic across builds and machines.

IDs are created using babel-unique-id. See their docs for options you can pass to the Babel plugin.

2. Capture data loaded on server side

The data which is loaded on the server needs to be sent to the browser so it can be used again when hydrating the app.

The first step is to capture this data on the server.

Create a DataExtractor and wrap the app with its .collectData() method. Then call the extractor's .getScript() method to get HTML to add to the server response.

// Server-side code import { DataExtractor } from 'react-lazy-data/server'; import { renderToStringAsync } from 'react-async-ssr'; import App from './App.js'; async function render() { const extractor = new DataExtractor(); const html = await renderToStringAsync( extractor.collectData( <App /> ) ); return ` <html> <body> <div id="root">${html}</div> <script src="/bundle.js"></script> ${extractor.getScript()} </body> </html> `; }

The output of render() will be something like:

<html> <body> <div id="root"> <div>My name is bulbasaur</div> <!-- ^^^ Rendered HTML ^^^ --> </div> <script src="/bundle.js"></script> <script> (window["__react-lazy-data.DATA_CACHE"] = window["__react-lazy-data.DATA_CACHE"] || {}).data = { "pokemon": { // <-- ID of resource factory "1": { // <-- Serialized request "name": "bulbasaur" // <-- Data for this request } } } </script> </body> </html>

You can also get the raw data object by calling extractor.getData().

3. Load data into cache on client side

The data sent from the server must be injected into the app on client side before it is hydrated.

Run preloadData() and await its promise before ReactDOM.hydrate().

// Client-side code import React from 'react'; import ReactDOM from 'react-dom'; import { preloadData } from 'react-lazy-data'; import App from './App.js'; preloadData().then(() => { ReactDOM.hydrate( <App />, document.getElementById('root') ); });

This last step is optional if the data script is included in the HTML above the Javascript bundle script tag.

However, generally performance is better including the JS bundle script tag in the head of the HTML with <script async> or <script defer>, so the browser can start loading the bundle before it's parsed the rest of the HTML. In that case the bundled JS may execute before the data script, and so the app will attempt to hydrate without any data.

preloadData() tells the app to wait for the data before beginning hydration.

Versioning

This module follows semver. Breaking changes will only be made in major version updates.

Tests

Use npm test to run the tests. Use npm run cover to check coverage.

Changelog

See changelog.md

Issues

If you discover a bug, please raise an issue on Github. https://github.com/overlookmotel/react-lazy-data/issues

Contribution

Pull requests are very welcome. Please:

  • ensure all tests pass before submitting PR
  • add tests for new features
  • document new functionality/API additions in README
  • do not add an entry to Changelog (Changelog is created when cutting releases)

Keywords

Socket

Product

Subscribe to our newsletter

Get open source security insights delivered straight into your inbox. Be the first to learn about new features and product updates.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc