cli-engine

cli-engine copied to clipboard

windows installer

1

I think it would be best to build the windows installer on appveyor. We could follow almost everything that the yarn installer does here: https://github.com/yarnpkg/yarn/blob/d4370f815157ced77afbc75e2f2572a2c120647f/appveyor.yml#L19

jdx

I think we already have a CLI suite, we need to make sure we're properly notified when something breaks

jdx

stdout/stderr, exit codes

jdx

would be nice to have both for plugins and core

jdx

not sure what this would look like yet, but possibly might have some overlap with https://github.com/heroku/cli-engine/issues/190

jdx

for cli-engine-command readme

jdx

possibly in a table on dev center?

jdx

I went through the help and these are my findings. We either create separate issues for these or just knock them off and mark as completed: CLI Manual Changes General...

jdx

jdx

somewhat inspired by https://github.com/josephfrazier/prettier_d one way we could dramatically speed up commands would be to use node cluster (or some kind of local daemon) to keep a group of command...

jdx