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

filter-dependent

v2.2.3

Published

Filters a list of files, leaving only those which transitively dependent on any of the files from the second list

Downloads

215

Readme

Filters a list of files, leaving only those which transitively dependent on any of the files from the second list.

Why this package was written?

Because I can! But also, because I failed to find anything like that, except jest-resolve-dependencies, which is not exactly what I need, and also have not very good algorithmic complexity (btw mine is O(n), where n is a number of nodes in a dependency graph fragment between sources and targers).

What problem it solves?

Similiar to changedSince – it allows you to find all files dependent from other files. And, therefore, skip other files.

For example, you can:

  1. Find all test files, which affected by git changeset, and should be running.
  2. Find all affected .stories.js files to build storybook only with affected components.

By doing that, you skip non-affected files and speed up your CI/build.

Features

  1. Supports js, jsx, ts, tsx.
  2. Fast.
  3. Resolves all symlinks to real filenames.
  4. Skip node_modules by default.

Example

Lets say we have four files:

  1. a.js depends on b.js and c.js
  2. b.js depends on d.js

Then:

import filterDependent from 'filter-dependent'

const filteredFiles = filterDependent([
    './a.js',
    './b.js',
    './c.js',
    './d.js',
], [
    'a.js',
    'c.js',
])

// → ['/abs/path/to/a.js', '/abs/path/to/b.js', '/abs/path/to/c.js']
// because `d.js` does not depend on `c.js` nor `a.js`

API

import filterDependent from 'filter-dependent'

const filteredFiles = filterDependent(sources, targets, options)

Where

sources – an array of file paths to be filtered. targets – an array of file paths to be used for filtering out sources. options.filter – function, which will be called on each found file (including sources and targers) to filter out some. (f: string) => f.indexOf('node_modules') === -1 && !f.endsWith('.css') by default. options.onMiss – function, which will be called instead of throwing an error. Arguments are: filename and dep – absolute path of processing file and unresolved dependendy in it

note: filter-dependent fails on first unresolved dependency (by default).