strange behavior with default middleware (rc-specific?)

[boneskull]

w/r/t the error with rc I was tracking down: the problem was I had a middleware configuration for rc:

this.use(cli.middleware.rc, {type: 'ini'}) //etc

I wanted an onload handler, but that's only allowed to be specified via configure(). So then I had both middleware() and configure() configurations, if that makes sense.

My WAG is that if a middleware returns a closure, cli-command is unable to detect whether or not it's been loaded already via the default loader (at about index.js:256), and does not throw.

The result of this was that running my program would fail silently. I would get absolutely no output, even from --help. The complete event was emitted, but I didn't know what to do with it.

Please let me know if this is an actual problem or user error, or a combination of the two. 😄

[tmpfs]

I wanted an onload handler, but that's only allowed to be specified via configure(). So then I had both middleware() and configure() configurations, if that makes sense.

That is annoying and can be easily fixed.

I am not entirely sure of the silent failure problem, are you using a completely custom middleware configuration, clearing the default list and adding your own manually? If so it might help to see all your use() statements.

A test case to reproduce the problem is of course welcome :)

[tmpfs]

The onload issue should be fixed in: e37df5b.

[boneskull]

ty