TJ
TJ
@aknuds1 I wouldn't say so but I don't think anyone else has hit the limit yet, that I'm aware of at least
Cool sounds good
any luck with this?
yep, just need to migrate my internal stuff first. It only supports time for now but I suppose that could change
it's both a bug and not a bug, throwing isn't great either, even node core has this issue but IMO it's a fundamental fail with callbacks
kinda, fixes the double callback but then you'll just get uncaughts, which is worse is hard to say :D haha both suck, but node core will just let it propagate/uncaught...
well they're arguably both wrong, but node itself is wrong. I'm not saying double callbacks are good, but they're no more harmful than exploding the entire process from a template,...
hmm must be something with swig, maybe we're not passing locals to it properly here, though the tests pass
im probably just going to delete this repo haha, it's easy enough to do whatever sort of flow control you want and listen() at the end
just with regular callbacks, or "async" etc, anything really: ``` js doSomething(function(){ app.listen(3000); }) ```