When an error occurs, Browserify 5.11.2 creates an empty output file. This should not happen, as it messes up make-based workflows.
$ cat >foo.js <<EOF
var quux = require('quux');
EOF
$ browserify foo.js -o bar.js
Error: Cannot find module 'quux' from '/private/tmp/foo'
at /usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:50:17
at process (/usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:119:43)
at /usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:128:21
at load (/usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:60:43)
at /usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:66:22
at /usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:21:47
at Object.oncomplete (fs.js:107:15)
$ ls -l | grep bar.js
-rw-r--r-- 1 mietek wheel 0 13 Sep 14:53 bar.js
Reactions are currently unavailable
When an error occurs, Browserify 5.11.2 creates an empty output file. This should not happen, as it messes up make-based workflows.
$ cat >foo.js <<EOF var quux = require('quux'); EOF $ browserify foo.js -o bar.js Error: Cannot find module 'quux' from '/private/tmp/foo' at /usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:50:17 at process (/usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:119:43) at /usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:128:21 at load (/usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:60:43) at /usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:66:22 at /usr/local/lib/node_modules/browserify/node_modules/resolve/lib/async.js:21:47 at Object.oncomplete (fs.js:107:15) $ ls -l | grep bar.js -rw-r--r-- 1 mietek wheel 0 13 Sep 14:53 bar.js