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

webpack-workerize-loader

v1.0.1

Published

inspired by [workerize-loader](https://github.com/developit/workerize-loader)

Readme

workerize loader for webpack5

inspired by workerize-loader

you need to know

  • target browser should support Proxy (bad news that Proxy is not ployfillable)
  • this loader will do soemthing in loader pitch function.
  • all function in worker will be wrapped by Promise
  • only one webworker will be created, all function will be called in the same webworker.(so ,they are series.)(TODO: need to support parallel)
  • you should not use default export in worker file. Loader only support named export.

demo

// index.ts
import type { WorkerFactory } from "../../dist/types";
import * as Worker from "./index.worker";
import type { expensive, addMy } from "./index.worker";
const startApp = () => {
  const instance = (
    Worker as unknown as WorkerFactory<{
      expensive: typeof expensive;
      addMy: typeof addMy;
    }>
  ).default();
  instance.expensive(100).then((res) => {
    console.log("res", res);
  });
};

startApp();
// call function in worker
// all function in worker will be wrapped by Promise
// block for `time` ms, then return the number of loops we could run in that time:
import { add } from "lodash-es";
import { addInFile } from "./utils";

const addC = () => {
  return add(1, 1);
};

export const expensive = (time: number) => {
  const start = Date.now();
  let count = 0;
  console.log("start");
  while (Date.now() - start < time) {
    count++;
  }
  console.log("end");
  return count;
};

export const addMy = (time: number) => {
  return add(1, 1) + addInFile() + addC();
};
// webpack.config.js

module.exports = {

  module: {
    rules: [
      {
        test: /\.worker\.ts$/,
        use: [
          {
            loader: path.resolve(__dirname, "../dist/index.js"),
            options: {
              inline: true,
            },
          },
        ],
      },

    ],
  },

};