Crash after successful rebuild

[mindjuice]

Recently, my project started crashing whenever I change any browser code. I'm running mimosa watch --server, so Mimosa kicks in and recompiles the file, runs Browserify, etc., but then a few seconds later I get a crash in mimosa-browserify (output below). Well, actually, the crash is in readable-stream, which is called from through, which is called from mimosa-browserify.

If I rerun the mimosa watch --server command, it builds again and everything is okay until I save another file.

Have you ever come across anything like this?

Thanks.

/vagrant/et-cloud/node_modules/mimosa-browserify/node_modules/browserify/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:355
  if (!state.ending && !state.finished)
            ^
TypeError: Cannot read property 'ending' of undefined
  at Transform.Writable.end (/vagrant/et-cloud/node_modules/mimosa-browserify/node_modules/browserify/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:355:13)
  at Stream.onend (stream.js:79:10)
  at Stream.emit (events.js:117:20)
  at drain (/vagrant/et-cloud/node_modules/mimosa-browserify/node_modules/through/index.js:34:23)
  at Stream.stream.queue.stream.push (/vagrant/et-cloud/node_modules/mimosa-browserify/node_modules/through/index.js:45:5)
  at f (/vagrant/et-cloud/node_modules/mimosa-browserify/node_modules/browserify/node_modules/module-deps/index.js:147:45)
  at result (/vagrant/et-cloud/node_modules/mimosa-browserify/node_modules/browserify/index.js:694:13)
  at /vagrant/et-cloud/node_modules/mimosa-browserify/node_modules/browserify/index.js:740:9
  at /vagrant/et-cloud/node_modules/mimosa-browserify/node_modules/browserify/node_modules/browser-resolve/index.js:189:13
  at /vagrant/et-cloud/node_modules/mimosa-browserify/node_modules/browserify/node_modules/resolve/lib/async.js:32:25
  at /vagrant/et-cloud/node_modules/mimosa-browserify/node_modules/browserify/node_modules/resolve/lib/async.js:59:30
  at /vagrant/et-cloud/node_modules/mimosa-browserify/node_modules/browserify/node_modules/resolve/lib/async.js:18:18
  at Object.oncomplete (fs.js:107:15)


npm ERR! et-cloud@0.0.1 dev: `mimosa watch --server`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the et-cloud@0.0.1 dev script.
npm ERR! This is most likely a problem with the et-cloud package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     mimosa watch --server
npm ERR! You can get their info via:
npm ERR!     npm owner ls et-cloud
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.2.0-23-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "run" "dev"
npm ERR! cwd /vagrant/et-cloud
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /vagrant/et-cloud/npm-debug.log
npm ERR! not ok code 0

[mindjuice]

Just an additional note. This only occurs if the server reload module has reload my server once before I change a client-side file. When this happens, mimosa restarts my custom node.js server again after browserify finishes regenerating the client side files. I don't know why it would restart my server though, since nothing being watched should have changed.

If I remove the "src" folder from my server reload watch list, then the server restart doesn't happen and this crash doesn't occur after browserify is done.

So as a workaround for now, when I want to work on the client, I use the following:

serverReload:
  watch:["server.js", "routes.js"]
  validate: true

When I want to work on the server, I use the following, so that it reloads the server when I change server files:

serverReload:
watch:["server.js", "routes.js", "src"]
validate: true

I just need to be careful not to save a client-side file or I get the above crash.

I'd still like to figure out the source of this problem, but for now I have a project to ship.