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

now-hls

v1.0.1

Published

A library that takes a .m3u8 and its' .ts files, and hosts it on ZEIT Now.

Downloads

3

Readme

now-hls

Take a .m3u8 file and its' .ts files, and host it on ▲ now.

npm version

NPM

Support goals

What now-hls can take care of, and what it will in future updates.

Make an issue to request further playlist types.

Debugging

now-hls uses the debug module to log to be silent and fast. Errors are always on however. Only "extra" logs are put in debug. If you want to enable extra logs, run nowhls through the DEBUG environment variable.

You should always enable this if you plan to contribute.

# unix, mac, linux
export DEBUG=nowhls

# windows shell
set DEBUG=nowhls

# windows powershell
$env:DEBUG = "nowhls"

# then just run normally
node example.js # or whatever your node script that uses now-hls is

Usage

const nowHls = require("now-hls");

nowHls('example-m3u8/cats.m3u8', function(url) {
  console.log(`url to hosted file: ${url}`)
}, '<NOW_TOKEN>');

if you need to get the content in it,

const nowHls = require("now-hls");

nowHls('example-m3u8/cats.m3u8', function(url, content) {
  console.log(`url to hosted file: ${url}`)
  console.log(`content: ${content}`)
}, '<NOW_TOKEN>');

Or alternatively, assuming you (or your team) stored the token in a ▲ now secret and exposed it as NOW_TOKEN...

now secrets add now-token <token>
$ echo "{ \
>  
>    \"env\": {
>       \"NOW_TOKEN\": \"@now-token\"
>     }
> }" >> now.json

you don't even need to specify the token!

const nowHls = require("now-hls");

// notice that <NOW_TOKEN> is gone!
// now-hls automatically grabs it uses process.env.NOW_TOKEN
nowHls('example-m3u8/cats.m3u8', function(url) {
  console.log(`url to hosted file: ${url}`)
});