the 8.13.0 version will report a error

[fakership]

It seems that the export object is not a function

[fakership]

when i take it back to 8.7.0, it will work!

[l3aconator]

I am getting this on the latest version too, works when the code isn't run through minifier

[verlok]

Hey guys, thank you for reporting this.
I'm afraid I need more information to help you.
Please tell me how you include LazyLoad (npm install? CDN script?) and how you use it.
Show me the code and I will be able to understand what happens.

[verlok]

Just to let you know, in version 8.13 and 10.13 I changed the content of the es2015.js file.
It used to be wrapped in UMD (Universal Module Definition), whereas now it's just a regular ES module.

[fakership]

I include LazyLoad by (npm install):

import LazyLoad from 'vanilla-lazyload';

This is the usage:

new LazyLoad({})

The lazyload.min.js will report a error;

[verlok]

Hey @fakership,
thanks for reporting it. I'll definitely check and get back to you.

[verlok]

Hey @fakership,

I've created this GitHub test repo in which I call LazyLoad as an ES2015 module, and everything works as expected.

So I think the problem might be related to something else you are using to bundle or minify your code.

What are you using? WebPack 4? Rollup.js? Babel is included in the mix?

Please share more information so I can investigate more.
Thanks

[verlok]

I was able to reproduce the bug using WebPack to bundle LazyLoad in this test repo.
https://github.com/verlok/lazyload-es2015-webpack-test
Now I'm going to fix it. I'm sure it's just a matter of webpack configuration.

[fakership]

yes, I bundle LazyLoad by webpack4.

[verlok]

I found the issue. It was a mistake in my package.json

[massic80]

Thanks!
I just found the trouble in my project, and the latest working release was the 8.12.
Looking forward for the 8.15 ;)

[verlok]

Just released 8.15.0 and 10.15.0 on npm.
The issue should be fixed now. Let me know!

[verlok]

I've tested it in this repo and checked that now it works correctly.

Thank you @fakership and @massic80 and @l3aconator for reporting your issues!