v4 upgrade (usage of =>) breaks easy browserify support #78
Comments
|
As I commented, duplicate of #70. I'm not interested in doing anything special for the browser. Please read: sindresorhus/ama#446 (comment) Sorry. You could always just stay on v3. It has the most common formats you'll need. |
arturi
added a commit
to transloadit/uppy
that referenced
this issue
Jun 14, 2017
we inline file-type module, as opposed to using the NPM version, because of this sindresorhus/file-type#78 and sindresorhus/copy-text-to-clipboard#5
Repository owner
deleted a comment from
pconerly
Oct 21, 2017
Repository owner
deleted a comment from
philipstanislaus
Oct 21, 2017
Repository owner
locked and limited conversation to collaborators
Oct 21, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
The v4 release does a great job to move on to using
=>in code. However, simple browserify fails now. I understand that browserify of this module is odd, but we do it. :-)Simply adding
babeltransform in package will make this way way easier for consumption. The other alternative for browserify consumers is to use complicated logic to specifically transform this module.is all what we mere mortals need @sindresorhus
The text was updated successfully, but these errors were encountered: