node package manager
It’s your turn. Help us improve JavaScript. Take the 2017 JavaScript Ecosystem Survey »


locust v1.0.1

npm install --save locust


Currently, you must use a Bash script to specify how Locust should behave. Generally, this means you should add some things to the .bashrc file in your home directory. You can easily get this done by using open ~/.bashrc. Once you make your changes, use bash ~/.bashrc to update.

Export the LOCUST_DIR variable to tell Locust where the local packages are.

export LOCUST_DIR="dev/modules"

Export the LOCUST_ROOT variable to tell Locust the directory in which LOCUST_DIR resides.


Export the LOCUST_ENABLED variable to indicate if Locust should be enabled.

export LOCUST_ENABLED="true"


If I want to use my local copy of the react package when I'm developing and testing, Locust can help.

require "locust"
React = locust "react"

Of course, Javascript developers can also benefit from Locust.

var React = locust("react");

without locust

Locust wants to improve your sanity when testing local changes as an open source developer. It does so by removing the ugly clutter of conditionally local dependencies.

React = require if process.env.LOCUST_ENABLED then "#{process.env.LOCUST_ROOT}/#{process.env.LOCUST_DIR}/react" else "react"

With Javascript, it's just as ugly.

var React = require(process.env.LOCUST_ENABLED ? process.env.LOCUST_ROOT + "/" + process.env.LOCUST_DIR + "/react" : "react");