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

@philgs/spawn

v1.0.0

Published

Launch a script into a separate process with custom environment variables

Downloads

3

Readme

Spawn

Launch a script into a separate process with custom environment variables

Usage

Define your custom environment variables in <app-root>/config/config.json using this format:

{
    "data": {
        "NODE_ENV": "development"
    }
}

You can supply an alternate path to the configuration file with the -c or --config command line flag (relative paths are resolved by using the current application directory (detected by looking for a node_modules subdirectory) as a base):

spawn -c ../some/other/config.json

Then use spawn in the "scripts" section of your package.json, like so:

{
    "scripts": {
        "start": "spawn nodemon ./scripts/launch-dev-server.js --exec babel-node",
        "test": "spawn mocha"
    }
}

Prior Art

This script is derived from a similar script. I would like to credit the original author(s), but I have lost all references to the original! (It may be a script that is generated by the Express app generator.)

License

The content of this repository is licensed under the 3-Clause BSD license. Please see the enclosed license file for specific terms.