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

progressive-hydration-component

v0.1.1

Published

Easily implement Progressive Hydration as React Component

Downloads

6

Readme

Progressive Hydration Component

Easily implement Progressive Hydration as React Component

Progressive Hydration?

Progressive Hydration is a term introduced at Google I/O 2019 by the concept to balance between client and server for the best performance.

By hydrate top priority component on server and then re-hydrate lesser priority component on the client.

By doing this, the first execution of JavaScript when landed on client is reduced which result better performance then lazily re-hydrate the component which is intersected on the client.

By implementing this strategy, the Time To Interactive is greatly improved, since only visible and top priority component is the only to be interactable while the other is active when need.

Benefit

  • Greatly improve JavaScript Time To Interactive
  • Kind of Lazy load interaction
  • Perfectly work with pre-render
  • Built for Next.js
  • Preact support
  • First class TypeScript
  • Tiny bundle size

The downside

To rehydrate the component, the extra wrapper is introduced to use ReactDOM.rehydrate which result an extra auto-generated <div> as a wrapper for progressive hydrated component.

Example

Progressive Hydration Component is imported as a React Component and introduced an extra removeEvent function to remove event from any React Component for pre-rendering and to be rehydrated later.

import ProgressiveHydration, { removeEvent } from 'progressive-hydration-component'

import Button from 'components/button'

const Component = () => (
    <ProgressiveHydration
        // When in view, component is re-hydrate with event.
        component={() => import('components/button')}
    >
        {/* Pre-render at built time, no JavaScript is executed during first load. */}
        {removeEvent(Button)}
    </ProgressiveHydration>
)
Note: This example is tested with Next.js

Resources