Latest babel-preset-env (7.4.3) breaks this plugin

[TheLudd]

I believe this change in babel-preset-env babel/babel#9781 breaks this plugin. Re-create by upgrading babel-preset-env in this package and run the tests.
I tried going through the code in order to find how to fix it but I didn't manage.

[MarshallRJ]

I am encountering the same issue.

[TheLudd]

Managed to solve it in #74

[ljharb]

#70 already solves it.

[TheLudd]

@ljharb Comitted in october. I wonder what the hope of a merge is
@59naga Are you notified about this?

[ljharb]

They’ve been tweeted at and emailed, since October.

[TheLudd]

@lijunle Are you able to review/merge/release?

[lijunle]

Hi, all. I found that I have NPM package management access. So, I directly merged #70 into my personal branch and publish it as version 1.0.1. Please check if it works.

@59naga If you are reading this comment, maybe you want to merge back my personal branch to master.

[lijunle]

Follow up: version 1.0.1 is unpublished due to #76

[lijunle]

Try version 1.0.2 to check if it mitigate this issue.

[pravi]

@lijunle looks like this plugin don't work well with @babel/plugin-transform-modules-umd (or even rollup with babel plugin for that matter)

umd module throws "Uncaught ReferenceError: module is not defined" in browser console. The same worked with babel 6 earlier.

For autosize 4.0.3:

babel 6 has,

(function (global, factory) {
if (typeof define === "function" && define.amd) {
 define(['module', 'exports'], factory);

But babel 7 has,

(function (global, factory) {
if (typeof define === "function" && define.amd) {
 define(["exports"], factory);

see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990458 for details.

In the end, I removed add-module-exports plugin and used rollup to generate umd, which worked.

Update: it looks like a known limitation of babel umd plugin babel/babel#10696