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 🙏

© 2026 – Pkg Stats / Ryan Hefner

react-pwa-app

v2.2.3

Published

react-pwa-app React component

Readme

ReactPwa light e simple

  • v2 Minor released now!
  • build using rollup

install

npm install react-pwa-app

or

yarn add react-pwa-app

react.js example

  • add in root index.html this line
<head>
  <link rel="manifest" href="%PUBLIC_URL%/manifest.webmanifest" />
</head>

next.js example _app.js

import Head from 'next/head'

<Head>
  <meta name="description" content="Generated by create next app" />
  <meta name="keywords" content="Keywords" />

  <link rel="icon" href="/favicon.ico" />
  <meta charSet="utf-8" />
  <meta httpEquiv="X-UA-Compatible" content="IE=edge" />
  <meta
    name="viewport"
    content="width=device-width,initial-scale=1,minimum-scale=1,maximum-scale=1,user-scalable=no"
  />
  
  {/* dont forget */}
  <link rel="manifest" href="/manifest.webmanifest" />
</Head>

manifest

  • put all your icons inside /public/icons and enter them with their respective sizes in public/manifest.webmanifest

usage:

import React from "react";
import ReactDOM from "react-dom";
import ReactPwa from "react-pwa-app";

ReactDOM.render(
  <ReactPwa
    test //is to install in localhost, not required
    suspense={<>
      a preloader to load the service worker in the application 
      is the best way to not overload with component calls.
      this ensures that the rest of the application only loads after the sw is checked
      default is children
    </>}
    config={{
      swUrl: "/service-worker.js", // sw file in public default is service-worker.js
      onUpdate: (reg) => {
        alert("sw cache was updated");
        console.log(reg);
      },
      onSuccess: (reg) => {
        alert("sw success installed");
        console.log(reg);
      },
      onError: (reg) => {
        alert("sw error to install");
        console.log(reg);
      },
      onPrompt:(e) => {
        if(e.outcome === 'accepted'){
          console.log('user click on install and accept')
        }
        if(e.outcome === 'dismissed'){
          console.log('user click on install and refuse')
        }
      },
    }}
  >
    <App />
  </ReactPwa>,
  document.getElementById("root")
);

in your component

import { usePwa } from "react-pwa-app";

const App = () => {
  const pwa = usePwa();

  console.log(pwa.registration); // ServiceWorkerRegistration

  return (
    <>
      <p>
        pwa.isInstalled: <b>{pwa.isInstalled}</b>
      </p>
      <p>
        pwa.supportsPWA: <b>{pwa.supports ? "Sim" : "Não"}</b>
      </p>
      <button onClick={pwa.install}>install app</button>
    </>
  );
};

Some tips

  1. service worker will be generated in the public folder

  2. manifest.webmanifest will be generated in the public folder

  3. service-worker.js needs at least 3 simple configurations. addEventListener('install' | 'activate' | 'fetch' )

  4. you can add pushnotifications support using addEventListener('push' )

  5. to get started use my service-worker.js inside /public

  6. post-install.js will be generated on root folder, you can use on create-react-app

postbuild

add script postbuild,

"scripts": {
  "postbuild": "node post-build.js"
}

this will help you auto-generate the application build routes, and also a new cachename to update the front whenever you update the app to a new version.

yarn add -D glob

you need to install glob to auto generate or customize this file