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

transcoded-client

v1.4.5

Published

Transcoded.io client for front-end frameworks, Node and browser

Downloads

36

Readme

Future-proof your static resources with a single line of code

Installation - NPM

npm i transcoded-client

Usage

The package requires that you have obtained a free Transcoded ID from our website, for access to transforms, storage and distribution of transcoded resources.

This ID must be passed, with the original resource URL and any options, to the resource constructor.

Options should be in the following format:

const options = {
    userAgent: <string>, //optional on client side, required in Node server side implementations
    width: <number>, //optional, default original width, sets required pixel width of resource
    quality: <number> //optional, default 80, sets required quality (and file size) of resource
};

Any errors in implementation will log to the console as warnings and the resource will fail over to the original URL, where possible.

Example - Node

const Transcoded = require('transcoded-client');

const exampleImageSrc = 'https://www.example/com/image1.jpg';

const options = {
    //Usage in Node requires a user agent string
    userAgent: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.111 Safari/537.36'
};

const futureProofSrc = Transcoded.imageSrc(exampleImageSrc, <TranscodedID>, options);

Example - ES6 (React)

import { imageSrc } from 'transcoded-client';

const small = '300.jpg';
const medium = '768.jpg';
const large = '1280.jpg';

//User agent string is not required in client side operations

const FutureProofResponsiveImage = () => (
    <img
        src={imageSrc(small, <TranscodedID>)}
        srcSet={`${imageSrc(small, <TranscodedID>)} 300w, ${imageSrc(medium, <TranscodedID>)} 768w, ${imageSrc(large, <TranscodedID>)} 1280w`}
    />
);

Example - Browser

<script src="https://unpkg.com/[email protected]"></script>

Browser usage in this fashion is currently blocked by an upstream dependency and will be offered in a future version.