Edit by @goto-bus-stop: This should be SOLVED in Uppy 1.9.1. Please ensure you have the latest versions by doing
npm install uppy@latestif you are using theuppypackage, or for each plugin by doingnpm install @uppy/PLUGINNAME@latestif you are using individual plugin packages.
what happen with the new version?

same error.
all libraries are affected with the new version.
is there a temp workaround? @ptgamr
i tried witht these versions
"@uppy/aws-s3": "^1.4.1",
"@uppy/core": "^1.7.1",
"@uppy/dashboard": "^1.5.2",
"@uppy/react": "^1.4.2",
stilll same issue
thank god for lock files. or else i would have had a hard time at this.
@zifahm for now, I stick with older version in the lock file (@uppy/core v1.7.1) ... don't delete the lock file, otherwise ^1.7.1 will resolve to 1.8, then it'll error. Or you have to pin the exeact version and do not use ^
Yup, Thanks mate @ptgamr
Sorry for the trouble! This is the result of a problem during the Lerna publish, we'll be publishing patch releases ASAP.
@arturi just published 1.9.1 which appears to fix the issue:

Thanks all for notifying us!
Most helpful comment
@arturi just published 1.9.1 which appears to fix the issue:

Thanks all for notifying us!