npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

react-preload-hook

v0.1.1

Published

Adds a preload hook to React Component which can be ignored on a second server render

Downloads

10

Readme

react-preload-hook

Adds a preload hook to React Component which can be ignored on a second server render

Problem

react-dom/server#renderToString is synchronous. All asynchronous state changes, like fetching data, will not end up in the initial render. So a second render pass is necessary after all asynchronous calls are resolved to render the complete html. But the problem is that you don't want to trigger all asynchronous calls again.

Solution

The temporary solution to the problem is to add a preload hook to the React Components that will only trigger in the first render pass. Temporary? Yes, renderToString is quite heavy and calling it twice feels like ineffective. I'm expecting better solutions to popup in the near future.

Example

// App
import React from 'react';

@preload
class App extends React.Component {

  preload() {
    console.log('fetch data');
    const { dispatch } = this.props;
    dispatch(fetchUsers());
  }

  render() {
    return (
      <h1>Hello</h1>
    );
  }
}


// Server
import express from 'express';
import React from 'react';
import { renderToString } from 'react-dom/server';
import PreloadContext from 'PreloadContext';
import App from './App';

const server = express();
const port = 3000;
server.use(handleRequest);
server.listen(port);

function handleRequest(req, res) {

  renderToString(<PreloadContext preload={true}><App /></PreloadContext>);

  // the first render pass will trigger the fetches
  // wait till all promises are resolve from the redux store
  // before rendering the second pass with a full store
  const promises = store.getState().pending.actions.map(action => action.promise);
  Promise.all(promises).then(() => {
    const html = mustache.render(template, {
      initialState: JSON.stringify(store.getState()),
      html: renderToString(<PreloadContext preload={false}><App /></PreloadContext>)
    });
    res.send(html);
  });

}