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

deps-patch

v0.2.0

Published

Allow to add dependencies not detected from code

Downloads

3

Readme

deps-patch

version status

A plugin for both browserify and depsify, to allow to add dependencies not detected from code.

Example

In the following example, entry.css depends upon entry-deps.css, and extra.css upon extra-deps.css.

We can make entry.css depends on extra.css using this plugin.

var reduce = require('reduce-css')
var path = require('path')

var b = reduce.create(
  'entry.css',
  { basedir: path.join(__dirname, 'src') },
  'bundle.css'
)
b.plugin('deps-patch')
b.bundle().pipe(b.dest(path.join(__dirname, 'build')))

// add dependencies
setTimeout(function () {
  b.emit('deps-patch.update', [
    // it claims that entry.css should depend on extra.css
    // even if entry.css does not do it in the code
    { file: 'entry.css', deps: ['extra.css'] },
  ])
}, 200)

The result would be something like:

.entry-deps{} /* from entry-deps.css */
.extra-deps{} /* from extra-deps.css */
.extra{} /* from extra.css */
.entry{} /* from entry.css */

Usage

The deps-patch.update event should be fired whenever you want to add new dependencies.

b.plugin('deps-patch')

b.emit('deps-patch.update', depsPatch)

depsPatch is an array of rows. A row is just an object with fields:

  • file: String. the file path to the dependent
  • deps: Array. an array of file path to modules the dependent should depend upon.