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 blade-cli and registers it as an executable), you can then run the following command, which is similar to bun add blade-cli or npm install blade-cli, except that it doesn't install blade-cli from npm, but instead uses your local clone of the package:
bun link blade-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 testsbun test# Alternatively, run a single testbun test -t 'your test name'