he/him 
`throw undefined` and `throw <literally anything other than an error instance>` are the bane of my existence
Show this thread
-
how about... Promise.reject(<thing that isn't an error object>)? Perfectly valid, but w/ async/await syntax... i like my catch block to get an error object
I wouldn't say that's valid at all. It's equivalent to doing `throw primitive`. You should wrap it in an Error instance.
-
-
agreed that you should, but the spec doesn't require it be an Error instance. and that's too badpic.twitter.com/wsd6bimZkQ
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.