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

dev-env-installer

v0.0.14

Published

[![Build Status](https://travis-ci.org/mulesoft-labs/dev-env-installer.svg?branch=master)](https://travis-ci.org/mulesoft-labs/dev-env-installer)

Downloads

1,691

Readme

dev-env-installer (beta)

Build Status

For listed NPM modules having GitHub URL and branch:

  • Clones repositories locally
  • Installs NPM dependencies for each repository
  • Cross-links dependencies for cloned repositories
  • Installs typings
  • Provides "pull all", "build all" and "test all" commands

Usage

  • Add installer as dev. dependency to a module
  • Add workspace.json to the root of the cloned module repository:
{
  "npm-module-name-1" : {
    "build" : "npm run build",
    "test" : "gulp test",
    "gitUrl" : "https://github.com/org/npm-module-1.git",
    "gitBranch" : "devBranch",
    "installTypings" : true
  },

  "npm-module-name-2" : {
    "build" : "gulp build",
    "gitUrl" : "https://github.com/org/npm-module-2.git"
  },
}

The only required field for module is gitUrl.

With current directory set to a root of the module repository:

dev-env-installer install:

  • Clones all repositories listed in workspace.json, does not clone repository if already exist in workspace root. If no gitBranch is specified, clones master branch. Uses --single-branch.
  • For each repository executes npm install
  • For each repository executes npm link
  • For each dependency <npm-dependency-name> of each repository, which is listed in workspace.json removes the one installed by NPM and executes npm link <npm-dependency-name>
  • For each repository having installTypings: true executes typings install

dev-env-installer pullall - for each repository in workspace.json in reverse order executes git pull

dev-env-installer buildall - for each repository in workspace.json in reverse order executes the command listed as build in workspace.json. Skips if no command specified.

dev-env-installer testall - for each repository in workspace.json in reverse order executes the command listed as test in workspace.json. Skips if no command specified.

Optional CLI parameters:

  • --workspace sets up workspace root. If not specified, workspace root is either a parent dir if executed for a module or current dir if no module is found.
  • --descriptor sets up workspace.json path. If not specified, is searched in the current dir, module dir or workspace root.