Fix iife build

[lmiller1990]

resolves #1553 , hopefully.

[lmiller1990]

not sure it's ideal to import across packages but 🤷 seems to work great here.

I don't know why this project is a mono-repo.

[afontcu]

hopefully

Is there any way to test it out?

[lmiller1990]

@afontcu I tested it in my browser by creating an index.html and having Vue globally available, and using the iife build - works fine.

I hope it doesn't break anything else. All tests are green... but they were before too. We probably need some way to test the iife build, but it's nothing something I can put time into right now. I guess we need to set up selenium with nightwatch, or something.

[afontcu]

@afontcu I tested it in my browser by creating an index.html and having Vue globally available, and using the iife build - works fine.

"it works on my machine!!" 😂

joking aside, build is already broken so as long as tests are green… 👍

[sullivanpt]

We probably need some way to test the iife build, but it's nothing something I can put time into right now. I guess we need to set up selenium with nightwatch, or something.

Actually we don't need full blown selenium. We can test the iife in node with karma + puppeteer -- we use karma + phantomjs but I don't recommend it because it's not maintained and going stale.

Anyway, if I have free time I'll try to pull this together. (nvm. the yarn+ts+flow learning curve is a bit much for me to contribute directly. sorry)

Thanks so much for fixing the IIFE so quickly!

[lmiller1990]

I will release early next week @sullivanpt !

If you need it now, clone the repo, yarn install && yarn build and grab the iife build from dist.