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 🙏

© 2025 – Pkg Stats / Ryan Hefner

webworker-redux-connected

v0.0.7

Published

Easy to use Web Worker connected with Redux.

Readme

webworker-redux-connected

Easy to use Web Worker connected with Redux.

🚧**Beta version not suitable for productin!**🚧

  • Webpack ✅
  • Rollup (Vite) ✅
  • other boundlers ❔❔❔ (testing)

Install

1) npm i webworker-redux-connected

2) You need to create a file that would be an entry point for a bundler to create chunks of modules for worker. Let's create src/worker.modules.ts.

ℹ️ Note: If you don't use TS it may have .js exstension.

3) Let's add an alias for the bundler that can easily find this module file.

for Webpack open webpack.config.js

module.exports = {
  (...)
  module: {
    (...)
    alias: {
      //ℹ️ Note: Alies name must be exactly "worker.modules"
      "worker.modules": path.resolve(__dirname, "src/worker.modules.ts"),
    },
  },
};

for Vite open vite.config.js

export default defineConfig({
  (...)
  resolve: {
    (...)
    alias: {
      //ℹ️ Note: Alies name must be exactly "worker.modules"
      "worker.modules": path.resolve(__dirname, "src/worker.modules.ts"),
    },
  },
  optimizeDeps: {
    //ℹ️ Note: It is needed to exclude it from optimizing pre-build since it
    //prevents resolving the file's path correctly.
    exclude: ["webworker-redux-connected"],
  },
})

Run first worker

  • Firstly you need to create a worker slice and apply its reducers to the application store

ℹ️ Note: configureStore adds Thunk middleware by default. If you don't have Thunk in your store you should add it.

import { buildWorkerSlice } from "redux-webworker-connected";

export const worker = buildWorkerSlice();
export const store = configureStore({
  reducer: {
    [worker.slice.name]: worker.slice.reducer,
  },
});
  • Now you are ready to execute some function in the React component

ℹ️ Note: Async/await syntax is not available yet

import { worker } from "./store";

const { exec } = worker.actions;
const { byId } = worker.selectors
const func = () => {
  console.log("hello world");
  return new Promise((resolve) => {
    setTimeout(() => resolve("test"), 2000);
  });
};


function App() {
  const dispatch = useDispatch<any>();
  const { data, pending } = useSelector((s: any) => byId(s, "1"));
  const onClick = () => dispatch(exec({ id: "1", func }));

  return (
    <>
      {pending ? <div>pending...</div> : <div>{data}</div>}
      <button onClick={onClick}>test</button>;
    </>
  );
}

Inject modules

Worker is run in a completely different context which is why the worker's function does not have access to anything outside its closure. However, you can statically define modules that should be imported to the worker's context. Then you can easily access those modules that are passed as a function's argument. Bundler does the job for you creating separate chunks for those modules and importing them to the worker context.

  • Let's add to our worker.modules.ts some modules you would like to use in the worker
import { v4 } from "uuid";

const modules = { v4 };

export type WorkerModules = typeof modules;
export default modules;
  • Now we can use uuid library in worker
import { WorkerModules } from "./worker.modules";

//ℹ️ Note: TODO implicit typing
const func = (modules: WorkerModules) => {
  const id = modules.v4();
  return Promise.resolve(id);
};

(...)