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

@beautinique/frontend-tryon-assets

v1.0.2

Published

The models and images of the Beautinique try-on: MediaPipe models, eye patterns, lip textures and sample models.

Readme

@beautinique/frontend-tryon-assets

The models and images the Beautinique try-on needs, in a package of their own (about 17 MB) so that they are not part of the code package (@beautinique/frontend-tryon), which changes far more often. No code is in here.

@beautinique/frontend-tryon loads them from a CDN (jsDelivr serves every npm package) by default, so an app does not need to install or copy anything. You only install this package to host the files yourself.

What is inside

| Folder | What | Used by | | --------------------------------- | ------------------------------------------------------- | ------------------------ | | models/face_landmarker.task | Face landmarks (3.6 MB) | lip, face and eye try-on | | models/hand_landmarker.task | Hand landmarks (7.5 MB) | nail try-on | | models/hair_segmenter.tflite | Hair segmentation (0.8 MB) | hair try-on | | images/models/{face,hair,hand}/ | The sample models of the "Choose a model" list (6 each) | the model list | | images/eye/<finish>/ | The previews of the eye patterns | the pattern picker | | images/lips/textures/ | The textures the lip finishes are drawn with | lip try-on |

How the code package finds them

By default https://cdn.jsdelivr.net/npm/@beautinique/frontend-tryon-assets@<version>/, with the exact version the code package was tested with (the version is in a constant, and a test of the monorepo fails if it is not the version of this package). The files never change inside a version, so the CDN serves them with a cache of one year (immutable).

To serve them from your own origin instead, copy the folders to a folder of your public files and give the try-on the address:

<TryOnModal assets={{ baseUrl: '/tryon-assets/' }} ... />

If they are somewhere that is not a plain folder (a bucket with hashed names, a bundler that renames assets), give a function that turns the path inside this package (models/face_landmarker.task, images/eye/...) into the address:

<TryOnModal assets={{ resolve: (path) => myCdn(path) }} ... />

Whatever the address, the server has to allow the origin of your app (Access-Control-Allow-Origin): the models are fetched, and the images are drawn on a canvas that the try-on reads back (for the snapshot). jsDelivr does; a static host of your own does when it serves the files from your own origin.

Changing a file

A file of a published version must not change (the CDN keeps it for a year). Put the new file in a new version of this package, and raise the version in the code package.

License

MIT for the images (see NOTICE.md); the models are Google's, under Apache 2.0.