Remove Babel requirement? about async-throttle HOT 6 CLOSED

Makes sense, yeah I'll remove the requirement hopefully later today, ping me if I forget :P

from async-throttle.

Okay actually it seems that @babel/preset-env still applies the regenerator transform for "targets": {"browsers": "last 2 versions"} so I'm tempted to keep @babel/runtime so that people don't have to go to the trouble of requiring regenerator-runtime/register themselves.

Also, the reason you were seeing that error is not because Babel isn't used server-side, it's because the runtime transform was applied to the code but babel-register is in devDependencies, I forgot to put it in primary dependencies.
Various other packages of mine have babel-register in dependencies which is why I wasn't getting this error myself.

So I'll upgrade to the latest @babel/runtime and put it in dependencies.

from async-throttle.

I guess another option is to use a conditional exports package and tell people to load the polyfills if necessary themselves...I dunno, what do you think?

from async-throttle.

🎉 This issue has been resolved in version 1.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

from async-throttle.

@jedwards1211 Awesome! Figured my PR was opinionated (don't use yarn for example...) but could be a reference. Appreciate the comments and thanks for pushing this out!

from async-throttle.

You're welcome!

from async-throttle.