Modernize setup, fix bundling issues

[edorivai]

Hi All :wave:

I've been joining @janpaepke to take a look at the entire setup of this library, to see if we can modernize things and make sure the lib works with a variety of setups. It should work seemlessly with

• UMD <script src='...' />, define(['scrollmagic'])
• CJS const scrollmagic = require('scrollmagic')
• ESM import scrollmagic from 'scrollmagic'

Work has started in the rollup-integration branch, but please bear with us as we work out all the kinks. For those interested, we're looking at using rollup for bundling.

TODO:

• [x] restructure the code to replace all //@includes with esm imports
• [ ] drop bower support
• [x] configure build outputs for esm, cjs, and umd
• [ ] configure entry points for plugins
• [ ] use unpkg instead of cdnjs for publishing umd bundles
• [ ] use version in package.json as much as possible - try using npm version as much as possible instead of gulp versioning mechanism
• [ ] replace custom replacements with rollup-plugin-replace
• [ ] replace production-build exclusions with if(__DEV__) blocks, which should be removed by uglify for the production builds
• [ ] figure out what to do with plugin warnings, banners
• [ ] replace jshint by prettier+eslint

[jonkwheeler]

Can we revisit this? @janpaepke

ScrollMagic would be great if fully ESM compatible at this point, including it's animation.gsap.js plugin. There's way too many work-arounds for this at this point.

[ppoulard]

👍

May I suggest too :

• [ ] Use classes instead of functions : var construct = function () {
• [ ] Use typescript instead of js : since all type descriptions are inert comments, they could be set in the code
• [ ] Use node EventEmitter (rollup can add it to the bundles)