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

@eyevinn/hls-proxy

v0.1.1

Published

NPM library for proxying HLS requests

Downloads

2

Readme

hls-proxy

License: MIT Slack

Node library to intercept and proxy HLS requests.

With this library you can easily set up a proxy server to intercept and change the contents of an HLS manifest.

Installation

npm install --save @eyevinn/hls-proxy

Usage

Setup a proxy and provide request handlers.

const { HLSProxy } = require("@eyevinn/hls-proxy");

const proxy = new HLSProxy(handlers);
proxy.listen(process.env.PORT || 8000);

When a client requests a HLS to http://localhost:8000/example/master.m3u8 the following will happen:

  1. Client will request the master manifest /example/master.m3u8 from the proxy
  2. The handlers.originHandler(request) is called is expected to return the base URL (ORIGINBASE) for origin requests.
  3. The master manifest is then fetched from <ORIGINBASE>/example/master.m3u.
  4. Master manifest is parsed and the handlers.masterManifestHandler() is called with the parsed manifest as an m3u object. It is expected to return the manifest to be recevied by the client.
  5. Client then request a media manifest /example/2000/2000.m3u8
  6. The origin handler is called as in 2.
  7. The media manfiest is then fetched from <ORIGINBASE>/example/2000/2000.m3u8
  8. Media manifest is parsed and the handlers.mediaManifestHandler() is called with the parsed media manifest as an m3u object. The handler is expected to return the manifest for the client.
  9. If the URLs to the segments have not been altered in the media manifest handler and a client tries to retrieve a segment from the proxy the following additional steps will take place.
  10. The origin handler is called as in 2.
  11. Then the segmentRedirectHandler() is called and this handler is expected to return the URL to the segment. A 302 redirect to this URL is then sent to the client.

Example

const { HLSProxy } = require("@eyevinn/hls-proxy");
const proxy = new HLSProxy({
  originHandler: async () => {
    return "https://maitv-vod.lab.eyevinn.technology";
  },
  segmentRedirectHandler: async (request, baseUrl) => {
    const redirectUrl = new URL(request.raw.url, baseUrl);
    return redirectUrl.href;
  }
});
proxy.listen(8000);

Point the video player to http://localhost:8000/VINN.mp4/master.m3u8 and it will fetch all manifests via the proxy and segment requests are redirected to https://maitv-vod.lab.eyevinn.technology.

See examples/rewrite.js for a working example where the segment URLs in the media manifest is rewritten to the origin URLs. And in examples/redirect.js you find an example of a 302 redirect.

Handlers interface

interface IHandlers {
  originHandler: (request: IProxyRequest) => Promise<string>;
  masterManifestHandler?: (request: IProxyRequest, baseUrl: URL, m3u: any) => Promise<string>;
  mediaManifestHandler?: (request: IProxyRequest, baseUrl: URL, m3u: any) => Promise<string>;
  segmentRedirectHandler?: (request: IProxyRequest, baseUrl: URL) => Promise<string>;
}

About Eyevinn Technology

Eyevinn Technology is an independent consultant firm specialized in video and streaming. Independent in a way that we are not commercially tied to any platform or technology vendor.

At Eyevinn, every software developer consultant has a dedicated budget reserved for open source development and contribution to the open source community. This give us room for innovation, team building and personal competence development. And also gives us as a company a way to contribute back to the open source community.

Want to know more about Eyevinn and how it is to work here. Contact us at [email protected]!