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

crushinator

v1.0.2

Published

Copies Lazo component dependencies based on component package.json meta data.

Downloads

10

Readme

Build Status

crushinator

Thank you, Bob Barker. I'm as happy as a girl can be. End statement.

Copies Lazo component dependencies based on component package.json meta data.

Usage

var crushinator = require('crushinator');

// arguments
// 1. application distribution/target
// 2. options
      - modulesDir: the directory that contains the node modules for the application; default 'node_modules'
      - versionResolver: function that resolves version conflicts; default most recent version (semver);
        should return module to use in application distribution; paramaters are module object and array of conflicts
        including module object
      - pathResolver: resolves src and path destinations when copying application dependencies
      - htmlImportsDest: application distribution target for html imports; default is application_dist/app/imports
// 3. callback

crushinator('app/dist', { modulesDir: 'app/node_modules' }, function (err, results) {
    if (err) {
        throw err;
    }

    // results: object of modules copied + meta data; key is module name
    // example results object
    {
        module_name: {
            version: "1.2.3", // version copied
            data: { }, // package.json contents
            path: 'a/b/c', // node module path
            versions: [], // versions of module found
            paths: [] // src, dest paths for directories copied based on lazo meta data in module package.json
        }
    }
});