Nick Mitchell
i think this is due to app/plugins/package.json's postinstall having some bash-isms?
it doesn't seem to work at all
`compose foo` will insert some boilerplate that is no longer supported by composer; in particular a `require` and `module.exports` are both now required parts of composition source https://github.com/ibm-functions/shell/blob/master/app/plugins/modules/editor/lib/placeholders.js
many of the sell docs and screenshots don't have "real modules" for the composer examples
(**note**: this issue pertains to doing an npm install from github, not from the prebuilt binaries stored on npmjs.com i.e. `@ibm-functions/shell`) running `npm install -g --verbose starpit/shell` takes 2 minutes...
they get stuck sometimes when i click on a wskflow node to drill down to an action
note how this line pulls out just the last action: https://github.com/ibm-functions/shell-composer-plugin/blob/master/lib/composer.js#L479 we need to deploy all actions. here is a test case: https://github.com/ibm-functions/composer/blob/master/samples/demo.js
this will give us windows coverage. the biggest work here probably will be figuring out how to run a local openwhisk on windows. it is possible, but our current tools/travis/setup.sh...
after 65c46832f4b114d27092cfd60c23a62fc3ec674d, where we started building against a dist build, the codecov numbers dropped; we probably aren't instrumenting the dist builds properly