Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/60651

Open in StackBlitz

commit: c112fa2

I'm afraid this still won't work out of the box.
While this isn't recommended for production use, it might not work if users share the link with others.
I'd prefer to stick with the old defaults when transforming script.

I wonder if we could do some basic user agent sniffing, defaulting to "current browser"?

I'm afraid this still won't work out of the box.
While this isn't recommended for production use, it might not work if users share the link with others.
I'd prefer to stick with the old defaults when transforming script.

In Babel 8 we bumped the default targets to defaults, it would be very confusing if Babel standalone changed the default targets in contrast with Babel core, since they share the same goal: convert codes for legacy browsers. If the new defaults target does not work for some users, they can always specify older targets such as ie: 7. After all, the whole targets option thing informs users that they chose the compilation targets, not us.

In the migration docs, we can put that if you want the old Babel 7 standalone behaviour, you can specify data-targets="ie 7", which is also the targets of how babel-standalone is built. If users ever pause like "wait, do I really need the IE 7 support?", I believe they will do the research and come up with a better targets than the Babel 7 defaults.

I wonder if we could do some basic user agent sniffing, defaulting to "current browser"?

I thought about it before, but the MDN docs (source) explicitly disapproves this approach, as browsers could pretend to be other browsers.

Docs PR is ready, PTAL: babel/website#3130

@JLHwung could you already prepare the backport PR?

@JLHwung could you already prepare the backport PR?

Thanks for the heads up, I do not recall that I have prepared a backport, will do it now.