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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@shren/worklet-loader

v2.0.0

Published

worklet loader module for webpack

Downloads

1

Readme

Worklet Loader

This loader loads imported scripts as a URL pointing to (or containing) a compiled module. That URL can be used to add worklet modules.

NOTE! At the moment, this is basically just a fork of worker-loader and probably shouldn't be used. It's possible that, at some point, worker-loader will support worklets and this loader will be obsolete. It's also possible that there are worker-specific things that this package does that breaks worklets for one reason or another. So be careful!

Install

npm i -D worklet-loader

Usage

Inlined

App.js

import workletUrl from 'worklet-loader!./Worklet.js';

Config

webpack.config.js

{
  module: {
    rules: [
      {
        test: /\.worklet\.js$/,
        use: { loader: 'worklet-loader' }
      }
    ]
  }
}

App.js

import workletUrl from './file.worklet.js';

const audioCtx = new AudioContext();

audioCtx.audioWorklet.addModule(workletUrl).then(() => {
  // Do stuff with the now-registered processor
});

Options

|Name|Type|Default|Description| |:--:|:--:|:-----:|:----------| |name|{String}|[hash].worklet.js|Set a custom name for the output script| |inline|{Boolean}|false|Inline the worklet as a Blob| |publicPath|{String}|null|Override the path from which worklet scripts are downloaded|

name

To set a custom name for the output script, use the name parameter. The name may contain the string [hash], which will be replaced with a content dependent hash for caching purposes. When using name alone [hash] is omitted.

webpack.config.js*

{
  loader: 'worklet-loader',
  options: { name: 'WorkerName.[hash].js' }
}

inline

Inline the worklet as a Blob with the inline parameter

webpack.config.js

{
  loader: 'worklet-loader',
  options: { inline: true }
}

publicPath

Overrides the path from which worklet scripts are downloaded. If not specified, the same public path used for other webpack assets is used

webpack.config.js

{
  loader: 'worklet-loader'
  options: { publicPath: '/scripts/worklets/' }
}

Examples

Integrating with TypeScript

You will need to define a custom module for the exports of your worklet files

typings/custom.d.ts

declare module "*.worklet.ts" {
  const exportString: string;
  export default exportString;
}

App.ts

import fooBarWorkletUrl from 'worlet-loader!./fooBar.worklet.ts'

const audioCtx = new AudioContext();

// @ts-ignore: AudioContext.audioWorklet is not available as a type yet
audioCtx.audioWorklet.addModule(fooBarWorkletUrl).then(() => {
  // Do stuff with the now-registered processor
});