Files
meteor/tools/tests
David Glasser 64d939acb2 Add a lot more buildmessage captures
Many of these (mostly in top level commands in commands-packages.js) are
not super well thought out: they use a new "doOrDie" helper to run some
function in a capture and exit if there are any messages.  We really
need to get a little more thoughtful about the big picture of error
handling (combining "build" errors, network errors, catalog errors,
etc). But this at least allows the addition of more buildmessage
assertions.

At the very least, this ensures that if you edit a package.js in a local
package while "meteor run" is running, that instead of crashing the tool
it properly shows the buildmessage and lets you fix the issue.
2014-08-11 17:06:28 -04:00
..
2014-06-25 17:33:55 -07:00
2014-08-11 17:06:28 -04:00
2014-06-24 16:49:19 -07:00
2014-03-14 18:50:48 -07:00
2014-06-17 14:26:29 -07:00
2014-06-17 15:28:19 -07:00
2014-06-16 18:15:38 -07:00
2014-06-26 17:32:17 -07:00
2014-07-28 20:45:08 -07:00
2014-06-26 17:32:17 -07:00
2014-05-28 19:05:27 -07:00