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

@satoshibits/vite-plugin-worker-dev

v1.0.3

Published

Fixes web workers in development mode using esbuild

Readme

Vite Worker Plugin

A Vite plugin that fixes web worker issues in development mode, particularly the common Uncaught SyntaxError: Cannot use import statement outside a module error.

Problem

Vite handles web workers differently in development mode compared to production:

  • In production, Vite bundles web workers and automatically adds the necessary configurations
  • In development, Vite doesn't process workers the same way, leading to errors when using import statements in classic workers

Solution

This plugin automatically transforms classic web workers to use { type: 'module' } in development mode, ensuring consistent behavior between development and production builds.

Installation

npm install vite-worker-plugin --save-dev

Usage

Add the plugin to your vite.config.ts file:

import { defineConfig } from "vite";
import viteWorkerPlugin from "vite-worker-plugin";

export default defineConfig({
  plugins: [viteWorkerPlugin()],
});

Features

  • Automatically transforms new Worker() calls to use { type: 'module' } in development
  • Handles both string literals and variable-based worker paths
  • No configuration needed, works out of the box

Example

Before:

// This code works in production but fails in development
const worker = new Worker("./my-worker.js");

After:

// The plugin transforms this during development
const worker = new Worker("./my-worker.js", { type: "module" });

Notes

  • The plugin only applies transformations in development mode
  • For complex worker instantiation patterns, you may need to manually add { type: 'module' }

License

MIT