Add UMD support and export WOW class as default

[cusspvz]

Implementation referred on issue #228

[cusspvz]

@graingert Really? Didn't knew about that, didn't code on CS for about probably a year. Is there any easier change?

Inspite it does or not, this does the job.

[samhavens]

Is this why I have to write

import container from 'wowjs';
const WOW = container.WOW;

...when using WOW through NPM/Browserify?

[graingert]

@samhavens nope, you only need to write:

import Wow from 'wow.js';
new Wow(...);

[graingert]

@samhavens you're missing the "." between wow and js. This gets you the official https://wow.js.org version.

[samhavens]

So you npm install works, but when you bring it in, you use the period? Or
did I install some alternate version?
On Fri, Jul 22, 2016 at 10:06 AM Thomas Grainger [email protected]
wrote:

@samhavens https://github.com/samhavens nope, you only need to write:

import Wow from 'wow.js';new Wow(...);

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#249 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AG5W5TqlMARHJccRO8twfCxGQSy-Mz1sks5qYPiNgaJpZM4Icdgp
.

Sam Havens CTO
mobile: 818.590.0484
address: 23480 Park Sorrento 125B | Calabasas, CA 91302
web: carlabs.com
email: [email protected]

[graingert]

@samhavens you need to npm install --save wow.js

[graingert]

when you drop the "." you have to release your source under the GPL.

[samhavens]

Wow! Thanks
On Fri, Jul 22, 2016 at 10:08 AM Thomas Grainger [email protected]
wrote:

@samhavens https://github.com/samhavens you need to npm install --save
wow.js

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#249 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AG5W5RXgGYsv8zqb1Y0hYYwv7nwm2TOUks5qYPkYgaJpZM4Icdgp
.

Sam Havens CTO
mobile: 818.590.0484
address: 23480 Park Sorrento 125B | Calabasas, CA 91302
web: carlabs.com
email: [email protected]