This example
cli.table(users, {
name: {
minWidth: 7,
},
company: {
get: row => row.company && row.company.name
},
id: {
header: 'ID',
extended: true
}
}, {
printLine: this.log,
...flags, // parsed flags
})doesn't match the signature table(data: any[], inputOptions?: Partial<TableOptions>)
wait, maybe it's me. maybe I need to
npm update
1 sec
building it on a linux box now. FYI, it failed because it requires
makensis. Would be a good idea to include it as a dependency or document it
@samuela Check out ( https://oclif.io/docs/hooks )
- init - runs when the CLI is initialized before a command is found to run
- prerun - runs after init and after the command is found, but just before running the command itself
- command_not_found - runs if a command is not found before the error is displayed You can add custom hooks that you can then invoke within an individual command.
You can also create a custom hook that is invoked on each command you'd like it to run on.
Example:
class HelloCommand extends Command {
async run() {
// Custom Hook event (auth:github)
await this.config.runHook("auth:github");
const { flags } = this.parse(HelloCommand);
const name = flags.name || "world";
this.log(`hello ${name} from ./src/commands/hello.js`);
}
}
Anyone here know how to swap out the oclif log-driver? I've been wanting to use ( https://github.com/winstonjs/winston ) as the default driver and also customize some of the log-levels. Documentation doesn't really have much detail in this section.
Thanks I'll try that out @jdxcode
Would you also have any examples for Base Classes in Javascript vs Typescript?
i.e
Would you also have any examples for Base Classes in Javascript vs Typescript?
i.e
export default abstract class extends Command {
static flags = {
loglevel: flags.string({options: ['error', 'warn', 'info', 'debug']})
}
log(msg, level) {
switch (this.flags.loglevel) {
case 'error':
if (level === 'error') console.error(msg)
break
// a complete example would need to have all the levels
}
}
is there away . to read an input stream using oclif i.e.
./bin/run foo < ./data/bar
process.stdin
please post anything new there. It's more like a forum so it should be easier to follow individual discussions and browse past conversations than a single chat
Hi everyone, I've recently been hitting this error when running tests for our Oclif CLI:
(node:29441) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
at _addListener (events.js:280:19)
at WriteStream.addListener (events.js:297:10)
at WriteStream.Readable.on (_stream_readable.js:772:35)
at Snapshot._swallowEPIPE (/Users/djones/Code/percy-agent/node_modules/@oclif/command/lib/command.js:133:24)
at Snapshot.init (/Users/djones/Code/percy-agent/node_modules/@oclif/command/lib/command.js:67:14)
at Snapshot._run (/Users/djones/Code/percy-agent/node_modules/@oclif/command/lib/command.js:33:24)
at Function.Command.run (/Users/djones/Code/percy-agent/node_modules/@oclif/command/lib/command.js:155:16)
at <anonymous>You can get the full backtrace there with --trace-warnings turned on. And then after a wee bit of googling I noticed the Heroku CLI has actually been getting the same warnings recently https://ci.appveyor.com/project/heroku/heroku-cli-command/branch/master#L174
Has anyone seen this before? It seems to trace back to here https://github.com/oclif/command/blob/3c0bafd840b663f34286a9b1cb84aaee368a210d/src/command.ts#L178-L182
this looks very relevant too forcedotcom/cli#30
I think it may have been introduced with oclif/command#54 but I'm gonna revert to an older version of
@oclif/command and see if that fixes it.
ok, I have reverted to
@oclif/command 1.5.10 (which doesn't include PR #54 above) and the warning has gone.
@jdxcode you'll probably be interested in ^ looks like this particular error has not only affected our CLI but the force.com and Heroku CLIs too. oclif/command#54 is the root of the issue.
i thought i was being super awesome and make some clis, but then people said clis are dead, long live irc, i mean slack.... it seemed obvious 2y ago, but i still search and see no oclif-slack, is there some other secret sauce?
anyone know of some glue? im using botkit to build eggdrops ;)
Hi, I am new to Oclif, I got my first few commands in for a multicommand setup, the seem to work as intended with npm link.
Now I have to build a .deb for it. The build seems to work but when I install it on my machine, none of my commands are there.. Is there somewhere I have to define that it has to look into ./src/commands?
Now I have to build a .deb for it. The build seems to work but when I install it on my machine, none of my commands are there.. Is there somewhere I have to define that it has to look into ./src/commands?
anyone knows why ?
I developed a new package which i hope to use in my project with
npm install. The IDE says no errors , but when I run ./bin/run, it failes with MODULE_NOT_FOUND
Also, are there any good tutorials I can look at? Thanks in advance. :)
Has anyone integrated Yeoman with oclif command? I tried following the pattern used in oclif, but that is throwing a circular dependance
An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details. You can do this from the Heroku CLI with the command
It's back again.