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

supported

v0.7.5

Published

## Usage

Downloads

7

Readme

supported CI

Usage

npx supported <path/to/node_module>
npx supported <[array/of/node_modules]>

Optional Flags

The --current-date (-c) flag enables a form of limited time travel, and attempts to run the tools internal date calculations based on a specified date, rather then the current date.

Some examples:

  • --current-date="March 31, 2011" runs the tool as if it was March 31, 2021
  • --current-date="-3 weeks" runs the tool as if it was 3 weeks ago
  • --current-date="3 weeks" runs the tool as if it was 3 weeks from now

The date micro-syntax is described as:

Anything that new Date(input) parses, or if that fails it will assume to be a relative duration starting today parsed by parse-duration@^1.0.0's own micro-syntax.

--config-file

The --config-file(-f) enables to provide a path to the config file with the configurations mentioned here.

// config.json
{
  "custom": [
    {
      "dependencies": ["es6-promise", "rsvp"],
      "effectiveReleaseDate": "Dec 10 2022",
      "upgradeBudget": {
        "major": 4,
        "minor": 4,
        "patch": 4
      }
    }
  ]
}

As a node module

const { processPolicies } = require('supported');
const projectPaths = ['test/fixtures/unsupported-project', 'test/fixtures/supported-project' ];
const jsonResult = await processPolicies(projectPaths);
const projectPaths_2 = 'test/fixtures/unsupported-project';
const jsonResult_2 = await processPolicies(projectPaths_2);

Contributing

Clone the project, make changes and run the tests

git clone [email protected]:stefanpenner/supported.git
cd supported
yarn
yarn test

You can test against the local test fixtures

yarn start:registry
bin/supported tests/fixtures/supported-project
bin/supported tests/fixtures/supported-project tests/fixtures/unsupported-project