Failing test case for --debug --standalone

This demonstrates that with the --standalone option the UMD prelude
is adding a source line to the output. Since browserify doesn't change
the source map generated by browser-pack, which accommodates its require
runtime preamble, the result is a source map with an off-by-one error in
generated line numbers.

Previously, I attempted to offload --standalone onto browser-pack, but it
can be easily handled by just asserting that the additional prelude not
consume an additional source line.
Trim the UMD prelude to preserve lineno

Since browser-pack generates a source map when the debug option is
used we don't want to cause an additional source line to be added
or we'll have to process and fix the mappings.

Fixes the failing test case introduced in the previous commit.

Closes #390 -- I think?
2.35.2
update the defunctzombie links
using the upgraded browser pack
2.35.3
fix so that bundle() only fires once
2.35.4
upgrade browser-resolve and module-deps to get core modules installed into node_modules to resolve/ before the built-in shims
2.36.0
dropped browser-builtins, started doing that stuff in lib/builtins.js
Re-ordered callback fixing to before pending check to prevent double callback of pending bundles.
2.36.1

merged #537
merged
adding browserify-shim to transforms

browserify-shim v3 is a pure transform now and can be completely configured inside the package.json, unlike v2.
Merge pull request #538 from thlorenz/patch-1

adding browserify-shim to transforms
--budget
pass ArrayBuffer etc to the buffer tests
timers, streams from tar urls
float on patches