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

@probedjs/liberator

v0.2.2

Published

A stubornly opiniated environment for typescript libraries.

Downloads

5

Readme

Liberator

A stubornly opiniated environment for typescript libraries.

Using Liberator, you get:

  • Typescript.
  • A clean dist/ containing only what users of the library need.
  • Multiple build targets: esm, cjs, umd, prod, dev.
  • Test and coverage of both the source and the various built libraries.
  • Linting with eslint and prettier.
  • A clean repository without a bazillion config files.

Getting started

Here's the very few rules of thumb you need to keep in mind:

  1. All the source code goes in src/.
  2. src/index.ts is the sole entrypoint.
  3. Specs and tests can be either in src/ or tests/
  4. You do not publish the root repository, the dist/ directory itself is published.
  5. *.spec.ts runs on both the source and the built library.

From scracth:

npx @probedjs/liberator my-library
// or
npx @probedjs/liberator @my-scope/my-library

For an existing library

The easiest way to go about this is to create a placeholder library using npx @probedjs/liberator placeholderLib, and use it as a reference point.

Make sure you don't forget to set "private": true in your package.json so that you don't accidentally publish the source version of the library.

Configuring

For the time being, there is no configuration options whatsoever, since the main reason for it existing is to unify configuration accross a bunch of projects. That being said, if there is a demand for it, we can make things a bit more parametrizable.

Building

The following command will populate the dist/ directory with the library ready to be published.

npm run build

Testing

Testing the source. This will run all files named *.test.ts as well as *.spec.ts on the library as present in the src/ directory:

npm run test

Testing the built library. This will run all files named *.spec.ts on all versions of the library present in the dist/ directory:

npm run testDist

Misc.

Keeping Visual Studio Code happy

If you are using the eslint VSCode extension, you need to point it in the right direction:

.vscode/settings.json

{
    "eslint.options": {
        "configFile" : "node_modules/@probedjs/eslint-config/index.js"
    }
}