Needlessly Provoking Marsupials
    Share your code. npm Orgs help your team discover, share, and reuse code. Create a free org »

    locustpublic

    locust v1.0.1

    npm install --save locust

    setup

    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 LOCUST_ROOT="$HOME"

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

    export LOCUST_ENABLED="true"

    example

    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.

    require("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");

    Keywords

    none

    install

    npm i locust

    Downloadslast 7 days

    3

    version

    1.0.1

    license

    none

    last publish

    collaborators

    • avatar