Matt Edelman

Oh, sorry. I didn't register that the file: directive was in your package.json as opposed to a config file...

There is currently no configurability around the set of shortstop handlers registered. That would seem to be the only resolution to this issue.

Sounds like this issue should be filed against [confit](https://github.com/krakenjs/confit) instead?

I guess I need to reproduce this locally to fully understand what's happening... I'll give that a try tomorrow so I'm not talking out of my whatever.

OK. I have it reproduced locally. You just have to add a local module into the package.json... which should be clear enough from @jknight12882 's comments already. But for reading...

Submitted a PR to confit: https://github.com/krakenjs/confit/pull/65 This would give ability to configure a set of env properties for confit to ignore. Which in turn would prevent a shortstop-handler from attempting...

Made some changes to my fork of kraken-js to use the changes from the confit PR above: https://github.com/grawk/kraken-js/commit/f3a946f73cb67d4c1142b5e70bea83ddfcb77ab7 This would merge the options passed into the kraken constructor under `options.confit`...

I think I ran into this as well.. I introduced an error into the onconfig handler and got this output: ``` bash [development] Listening on http://localhost:8000 Possibly unhandled Error: boom...

I would have _assumed_ a process.exit on throwing that error ^

Hi @rhettl I'd like to help you with this. Do you think you can create a sample application that I can run which illustrates this issue?