enable esm transpilation - fixes IE11 compatibility.

[avilv]

No description provided.

[klarstrup]

4 releases since this PR went up, any feedback @krisk?

[avengerx]

Isn't this just a config setting and pull request sets this IE11 compatibiliuty "on by default"?

Just wondering if this should be a documentation issue or considered a bug.

[radhikagupta5]

Any update on when this would be merged and released? @krisk

Would like to use latest version of Fuse but unable to use since we need support IE11 as-well.

[krisk]

Could you not simply use fuse.common.js? See here

[avilv]

Could you not simply use fuse.common.js? See here

this would work for old webpack / browserify, but not for anything modern that uses the ESM output (i.e, webpack2, angular cli, react etc. )

[Qrymy]

@krisk
Hi, I'm using fuse.js, and great library, thanks!
And I'm facing ie11 build problem. I know I should use fuse.common.js, however I'm using with Next.js x TypeScript.
So there is no type definitions in fuse.common.js, So I suggest you two ideas.

1. Merge this pr
   This is most easiest way, but bundle size will be larger than now, and ie11 will be disappear soon (1 year or more...).

2. Create esm for ie11
   This way is so clever, react-hook-form is doing. For example,

import Fuse from 'fuse.js' // this is support except ie11
import Fuse from 'fuse.js/dist/fuse.ie11' this is support also ie11

If you adopt this way, normal bundle size will be same, and if ie11 disappear, you should remove as soon as possible.

If you think this way is good, I will make pr.

Thanks.

[mcrawshaw]

@krisk will @Qrymy suggestion work?

[Reached]

Could we get this merged in by any chance? :)

EDIT:
I just made my own fork, compiled with the changes from this PR, and can confirm that it solves compatibility issues in both IE11 and Edge