Nuked: Probably Microwaved

    TypeScript icon, indicating that this package has built-in type declarations

    5.3.4 • Public • Published

    Imperative CLI Framework


    Imperative CLI Framework is a command processing system that lets you quickly build customized command-line interfaces. Focus on adding functionality for your users rather than creating CLI infrastructure. We provide you with all the tools to get started building your own CLI plug-ins.

    Software Requirements

    • Install Node.js package manager on your computer. Node.js® is a JavaScript runtime environment on which we architected Imperative CLI Framework.

    • You must have a means to execute ".sh" (bash) scripts to run integration tests. On Windows, you can install "Git Bash", which is bundled with the standard Git installation - (choose the "Use Git and Unix Tools from Windows Command Prompt" installation option). When you run the integration tests on Windows, you must have Administrative authority to enable the integration tests to create symbolic links.

    Note: Broadcom Inc. does not maintain the prerequisite software that Imperative CLI Framework requires. You are responsible for updating Node.js and other prerequisites on your computer. We recommend that you update Node.js regularly to the latest Long Term Support (LTS) version.

    Install Imperative as a Dependency

    Issue the following commands to install Imperative CLI Framework as a dependency. Note that the registry URL differs between versions of Imperative CLI Framework.

    • Install @latest version:

      Be aware that if you update via @latest, you accept breaking changes into your project.

      npm install --@zowe:registry= --no-package-lock --force
      npm install --save @zowe/imperative
    • Install @lts-incremental version:

      npm install --@zowe:registry= --no-package-lock --force
      npm install --save @zowe/imperative@lts-incremental

    Build and Install Imperative CLI Framework from Source

    To build and install the Imperative CLI Framework, follow these steps:

    1. Clone the zowe/imperative project to your PC.
    2. From the command line, issue cd [relative path]/imperative
    3. Issue npm install
    4. Issue npm run build
    5. Issue npm run test

    To build the entire project (including test stand-alone CLIs): npm run build

    To build only imperative source: gulp build

    Run Tests

    Command Description
    npm run test Run all tests (unit & integration)
    npm test:integration Run integration tests
    npm test:unit Run unit tests

    Note: To run the integration tests via gulp, install all dependencies for test CLIs, build all test CLIs, & install all sample CLIs globally using the following sequence:

    1. gulp build:install-all-cli-dependencies
    2. gulp build:all-clis
    3. gulp test:installSampleClis

    Note: For more information about the tasks (details and descriptions), issue the following gulp command: gulp --tasks

    Sample Applications

    We provide a sample plug-in that you can use to get started developing your own plug-ins. See the Zowe CLI Sample Plug-in.


    We provide documentation that describes how to define commands, work with user profiles, and more! For more information, see the Imperative CLI Framework wiki.


    For information about how you can contribute code to Imperative CLI Framework, see CONTRIBUTING


    Imperative CLI Framework uses Semantic Versioning (SemVer) for versioning. For more information, see the Semantic Versioning website.

    Licencing Imperative CLI Framework

    For Imperative CLI Framework licensing rules, requirements, and guidelines, see LICENSE.


    npm i @zowe/imperative

    DownloadsWeekly Downloads






    Unpacked Size

    3.77 MB

    Total Files


    Last publish


    • joe_winchester
    • zowerobot
    • markackertbroadcom