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

launch-json

v1.0.1

Published

Loads Visual Studio Code's (vscode) launch.json environment variables so that you can run your node app from the command line

Downloads

16

Readme

launch-json

Helper library that loads the environment variables from Visual Studio Code's (vscode) launch.json into process.env.

Usage

In your startup file (e.g. server.js, index.js or app.js), just include the following line:

require('launch-json');

That's it! This module will then find the .vscode/launch.json file in your project and merge the environment variables into your process.env.

This will then allow you to run your node app from the command line without having to manually set the environment variables in your launch.json.

Why launch-json?

This library is designed specifically for users of vscode who store environment variables in their project's launch.json. There's a few scenarios where using this library might be useful:

  • You want to make sure your code runs the same outside of vscode (which starts node processes by default with --debug enabled)
  • You have Mocha tests (or tests from another test framework) which rely on environment variables
  • Your environment variables have colon's in them. These are a pain to export into environment variables on macos

Options

When required as above, this will load the default "launch" configuration from the .vscode/launch.json file. To choose a specific configuration, simply:

require('launch-json')('myconfig');

Example

Assume you have the following launch.json:

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "launch",
            "type": "node",
            "request": "launch",
            "program": "${workspaceRoot}/lib/index.js",
            "cwd": "${workspaceRoot}",
            "env": {
                "NODE_ENV": "local",
                "theFox":"red",
                "theDog":"brown"
            }
        },
        {
            "name": "dev",
            "type": "node",
            "request": "launch",
            "program": "${workspaceRoot}/lib/index.js",
            "cwd": "${workspaceRoot}",
            "env": {
                "NODE_ENV": "development",
                "theFox":"quick",
                "theDog":"lazy"
            }
        }
    ]
}

The following will work:

require('launch-json'); // launch is selected by default
process.env['NODE_ENV']; // local
process.env['theFox']; // red
process.env['theDog']; // brown

The following will work:

require('launch-json')('dev'); // dev will load
process.env['NODE_ENV']; // development
process.env['theFox']; // quick
process.env['theDog']; // lazy