bin: add citgm-all #27
Conversation
|
Express failed: Looks like the test suite for 4.13.3 fails on the current stable node (5.1) Chalk failed: Test suite is only failing inside of citgm. It looks like the color data that chalk is appending the strings is getting lost at some point. I assume this is because it is running in a child process. Will investigate #28 the project npm-run-all implemented this fix to keep colors on internal processes mysticatea/npm-run-all@736dee0 It look like there needs to be a refactor of how we handle spawning processes, and how we spawn npm commands. There appears to be quite a bit of overlap between npm-run-all and citgm, perhaps we can borrow some from that project (license is MIT) Colors failed See above bluebird failed TypeError: process.stdout.cursorTo is not a function Looks like some more weirdness with stdout, likely making assumptions that it is running top level yeoman-generator I think we likely want to be tracking yo, which is the cli tool, rather than yeoman-generator. The tests are failing regardless. Test suite on Master fails too. Looks like we found a breaking change :D redis fails don't have redis setup 📦 jquery fails handlebars fails v4.0.5 master Looks like handlebars is not doing so well right now :( yosay same problem as chalk mime AssertionError: 'audio/mp4' == 'audio/x-m4a' Does not look related to node |
|
/cc @jasnell |
|
woo! awesome |
663b128 to
805625c
Compare
805625c to
13c89cf
Compare
|
reopening |
This PR adds a new bin to the project
citgm-allBy default
citgm-allwill run the test suite of every package in the lookup table. If a custom lookup table is provided it will iterate across that instead.TODO:
ensure every package in lookup works(ish)