Problems using --watch with Mocha using a fresh oclif install
Just setup a brand new oclif Typescript project. I wanted my test suite to automaticaly re-run when a file has been changed. I've tried adding --watch to the mocha args which does trigger watch mode, but then when a file is changed, it prints 0 passing and I have to kill/restart…
Need some guidance on how to package a multi cli
Trying to wrap my head around how to test installing the cli without pushing to NPM just yet. Had a few colleagues try to install it via github (npm i -g /long/github/repo/url) and it seems to blow up at the prepack stage. I'm using TypeScript and I get a lot of errors where it…
Any guidance for large cli project ?
I am looking for guidance to build large cli project where each team will be in charge on various command thus i would like to strive for a modular / component model. At the moment all the command are stored within the commands folder which makes it hard to build complex…
I was just wondering if there's an easy way to accomplish this with OCLIF? I know that when generating a project, it gives you the choice of using either-or, but is there a documented way of migrating to typescript after the fact? Thank you!
Is it possible to create a multi command cli 'dynamically'?
With other cli frameworks (such as yargs), the cli is constructed at runtime not design time. Eg, to create a command you call something like yarg.command('name of command', other args).fluent call for other settings... However, my initial reading of oclif, is that you have to…