Support more extensions in register hook about async-to-gen HOT 2 CLOSED

I created a pull request with a fix that would not register async-to-gen when another hook is active, allowing a previous hook (babel etc) to be leading: #14

Maybe not the nicest of fixes, but after spending 2 hours on a solution I settled for that, as it just covers most use cases.

from async-to-gen.

I've changed the behavior of the register hook in #16 to apply to any compiled module rather than using require.extensions. This abstracts it away from the file extension so that it will just use whatever behavior node already uses. That means implicit support for .jsx and .es6 or .omgwtf if that's what you're into.

#16 also ensures this module's require hook doesn't clobber an existing one like Babel's, however the only way to accomplish that is by going second. Babel's transformer will run first. If you're already using Babel to handle JSX, then you're best off just handling async functions within Babel as well (use babel-preset-es2017) and probably just don't use this library at all. However this also means if you're using async-node by accident or otherwise that things won't break.

from async-to-gen.