JSPM

@ronin/cli

0.3.19
    • ESM via JSPM
    • ES Module Entrypoint
    • Export Map
    • Keywords
    • License
    • Repository URL
    • TypeScript Types
    • README
    • Created
    • Published
    • Downloads 107
    • Score
      100M100P100Q109140F
    • License Apache-2.0

    The command-line interface for RONIN.

    Package Exports

    • @ronin/cli
    • @ronin/cli/dist/index.js

    This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@ronin/cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

    Readme

    RONIN CLI

    tests code coverage install size

    This package exposes the ronin command, which you can run from your terminal to interact with RONIN.

    Setup

    You don't need to install this package explicitly, as it is already included in the RONIN client.

    However, we would be excited to welcome your feature suggestions or bug fixes for the RONIN CLI. Read on to learn more about how to suggest changes.

    Contributing

    To start contributing code, first make sure you have Bun installed, which is a JavaScript runtime.

    Next, clone the repo and install its dependencies:

    bun install

    Once that's done, link the package to make it available to all of your local projects:

    bun link

    Inside the @ronin/client repo (which imports @ronin/cli and registers it as an executable), you can then run the following command, which is similar to bun add @ronin/cli or npm install @ronin/cli, except that it doesn't install @ronin/cli from npm, but instead uses your local clone of the package:

    bun link @ronin/cli

    Transpilation

    In order to be compatible with a wide range of projects, the source code of the cli repo needs to be compiled (transpiled) whenever you make changes to it. To automate this, you can keep this command running in your terminal:

    bun run dev

    Whenever you make a change to the source code, it will then automatically be transpiled again.

    Running Tests

    The RONIN CLI has 100% test coverage, which means that every single line of code is tested automatically, to ensure that any change to the source code doesn't cause a regression.

    Before you create a pull request on the cli repo, it is therefore advised to run those tests in order to ensure everything works as expected:

    # Run all tests
    bun test
    
    # Alternatively, run a single test
    bun test -t 'your test name'