dev-bundle exposes the shell script that downloads the dev bundle. We need this
in a package because both star-translate and tools/bundler.js need access to it.
One bug (I think) was the the assetPath argument to walk() was getting stomped
on and therefore not being used, so I removed the argument. Another bug was that
the url for an asset was being set from the file's absolute path.
In addition to minor "make the tests match the code" changes, there's also:
- missing require('tar') in tarball download code
- fix an fd leak in the bundler that was causing EMFILE on mac
- switch run.js to listening for 'exit' to 'close' so that the end
of stdout/err can be read
- some concerningly necessary deletions of .build directories
Also, the version of cli-test.sh that runs against a fixed release is disabled,
since we're not building releases with the new package format for now.
This allows you to include "test helper" packages there which are only used in
test mode, as well as other internal packages which shouldn't be exported into
your app.
test-packages still tests them.
That brought in all of webapp, which only works on "type: traditional" targets,
not server-only.
(We really should split the Node DDP Client code from the Node DDP Server code
instead.)
(Maybe routepolicy should just be part of webapp, or webapp should depend on
routepolicy? It's awkward to need to list it separately in various places...)
Replace type: "bare" with type: "server" in attributes.json. This now just
means "only make one server process" rather than controlling the boot script.
Programs that are type: "traditional" that want to be a webapp now need to
explicitly depend on the webapp package.
It's implemented by the forceDisconnect method on streams. Fix forceDisconnect
on Node streams when forceDisconnect is called during the initial connection.
