special-case nodemon in scripts.start

[SomeKittens]

I'm a colossal idiot and set my npm start script to:

"start": "DEBUG=nbe NODE_ENV=development nodemon ./bin/www"

Later on, I picked up the project and ran nodemon, knowing it'd pick up whatever was in npm start automatically. You may start laughing now.

While I didn't quite get an infinite loop, I got this strange error:

sh: 1: NODE_ENV=development nodemon ./bin/www: not found
[nodemon] failed to start process, "DEBUG=nbe" exec not found
exception in nodemon killing node
TypeError: Uncaught, unspecified "error" event.
    at TypeError (<anonymous>)
    at emit (events.js:74:15)
    at ChildProcess.<anonymous> (/usr/lib/node_modules/nodemon/lib/monitor/run.js:119:11)
    at ChildProcess.emit (events.js:98:17)
    at Process.ChildProcess._handle.onexit (child_process.js:820:12)

It took me a bit of looking to realize just how dumb I was.

I propose a special case (to be titled "SomeKittens doesn't know node") where if nodemon is found in npm start, throw an error.