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

@x4trioz925c3/rls-parser

v1.0.3

Published

A comprehensive NodeJS release name parser.

Readme

Rls-JS Parser for Node.js

A comprehensive release name parser for Node.js, ported from the Go rls library. That AutoBRR uses.

Installation

npm install rls-parser

Usage

The library exports an Rls class. You should create an instance of this class and reuse it to parse release names.

Full Parse

const { Rls, ReleaseType } = require('./rls');

const rls = new Rls();

const title = "The.Creator.2023.PROPER.UHD.WEB-DL.2160p.HEVC.DV.HDR.EAC3.7.1.DL.Remux-TvR";
const release = rls.parseRelease(title);

console.log('--- Full Parse ---');
console.log('Type:', release.type);         // movie
console.log('Title:', release.title);       // The Creator
console.log('Year:', release.year);         // 2023
console.log('Resolution:', release.resolution); // 2160p
console.log('Source:', release.source);     // UHD.WEB-DL
console.log('Codec:', release.codec);       // [ 'HEVC' ]
console.log('Group:', release.group);       // TvR
console.log('Other:', release.other);       // [ 'PROPER', 'REMUX' ]

Fast "Type-Only" Parse

If you only need to determine the type of the release (e.g., for routing files) and don't need all the metadata, you can use the typeOnly option for a faster result. This skips the expensive title and unused-tag analysis.

const { Rls } = require('./rls');

const rls = new Rls();

const title = "The.Creator.2023.PROPER.UHD.WEB-DL.2160p.HEVC.DV.HDR.EAC3.7.1.DL.Remux-TvR";

// Pass the typeOnly option
const release = rls.parseRelease(title, { typeOnly: true });

console.log('\n--- Type-Only Parse ---');
console.log('Type:', release.type); // 'movie'
// Other fields may be empty or partially filled, but the type is reliable.
console.log('Title:', release.title); // '' (Title processing is skipped)

Running Tests

To run the integrated test suite, you need the tests.yaml file from the original project. Place it in the root directory and run:

npm test

Or to run verbosely

npm test -- --verbose