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

use-pipeline

v0.0.35

Published

A react hook that wraps the transformers.js pipeline API

Readme

usePipeline

This is a react hook that wraps the transformers.js pipeline API.

getting started

npm i use-pipeline @huggingface/transformers

minimal example

You can use the hook with just the task and the model_id of the model you want to use.

// App.jsx
const App = () => {
    const { pipe} = usePipeline(
        "text-classification", // task
        "Xenova/distilbert-base-uncased-finetuned-sst-2-english", // model_id
    );
    return <button onClick={() => pipe(['I love transformers.js']).then(console.log)}>run</button>;
}

A WebWorker is then automatically instantiated in the background, in which the calculations are performed.

use your own WebWorker

If you want to you can also use your own WebWorker.
Since working with WebWorkers is often a bit unfamiliar, I have tried to make it as simple as possible. In the WebWorker, all you need to do is to call the webWorkerPipelineHandler().onmessage.
As you can see, all the messaging between the app and the worker is abstracted away by the library.

Vite

// App.jsx
import { usePipeline } from "use-pipeline";

const App = () => {
    const worker = React.useMemo(
        () => new Worker(new URL("./worker.ts", import.meta.url), {
            type: "module",
        }),
        [],
    );
    
    const { pipe} = usePipeline(
        "text-classification", // task
        "Xenova/distilbert-base-uncased-finetuned-sst-2-english", // model_id
        {}, // transformers.js pipeline options
        worker
    );
    return <button onClick={() => pipe(['I love transformers.js']).then(console.log)}>run</button>;
}
// worker.js
import { webWorkerPipelineHandler } from "use-pipeline";
self.onmessage = webWorkerPipelineHandler().onmessage

Webpack

// webpack.config.js
module.exports = {
    experiments: {
        outputModule: true,
    },
    module: {
        rules: [
            {
                test: /\.worker\.js$/,
                loader: 'worker-loader',
                options: { type: 'module' },
            },
        ],
    },
};
// App.jsx
import { usePipeline } from "use-pipeline";
import Worker from './pipeline.worker.js';

const App = () => {
    const { pipe} = usePipeline(
        "text-classification", // task
        "Xenova/distilbert-base-uncased-finetuned-sst-2-english", // model_id
        {}, // transformers.js pipeline options
        Worker
    );
    return <button onClick={() => pipe(['I love transformers.js']).then(console.log)}>run</button>;
}
// pipeline.worker.js
import { webWorkerPipelineHandler } from "use-pipeline";
self.onmessage = webWorkerPipelineHandler().onmessage

options.device

There is one addition to the transformers.js pipeline API. The device option also accepts an array of devices instead of just one device as string. The library will then try to find the first device in the array that is supported by the client:

const { pipe} = usePipeline(
    "text-classification", // task
    "Xenova/distilbert-base-uncased-finetuned-sst-2-english", // model_id
    {
        device: ['webgpu', 'wasm']
    },
);

In this case, if the client supports WebGPU, it will use WebGPU, otherwise it will use wasm.

!!! This feature is highly experimental. For now, only the webgpu check does work. It might change in the future or will be removed.