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

redux-bundler-worker

v0.0.3

Published

Utilities for running a redux-bundler app inside a worker

Readme

redux-bundler-worker

Utilities for running a redux-bundler app inside a worker. Largely for demonstration purposes, I have not shipped any production apps built this way.

But it demonstrates a rather feature-complete mechanism for doing so. Utilizing a worker for the entire redux application and then simply doing rendering in the main thread.

install

npm install redux-bundler-worker

example

In the main thread:

import { render, h } from 'preact'
import { Provider } from 'redux-bundler-preact'
import RootComponent from './components/root'
import { getStoreProxy } from 'redux-bundler-worker'

// init our worker
const worker = new Worker('/build/worker.js')
// pass the worker into getStoreProxy to
// get something that mimics the API of a
// redux store created by redux-bundler
const storeProxy = getStoreProxy(worker)

// render our root component passing the proxy
// as if it were the store to Provider:
render(
  <Provider store={storeProxy}>
    <RootComponent />
  </Provider>,
  document.getElementById('app')
)

In the worker:

import getStore from './src/bundles'
import { setUpWorker } from 'redux-bundler-worker'

// setUpWorker expects a function it can call *with* initial
// data that will return our redux store. This is what is returned
// by calling redux-bundle's `composeBundles` function anyway.
setUpWorker(getStore)

change log

  • 0.0.3 - now handling scroll position restoration
  • 0.0.2 - initial public release

credits

If you like this follow @HenrikJoreteg on twitter.

license

MIT