Webpack + gsap error

[Torrfura 2 Likes (Newbie)]

Hi,

 

I have a problem using gsap through bower, compiled with webpack. My shim looks like this:

webpack: {
  defaults: {
    plugins: [
      new webpack.ProvidePlugin({
        ...
        '$': 'jquery',
        'TweenLite': 'gsap'
        ...
      })
    ],
    externals: {
      jquery: 'window.jQuery',
      'TweenLite': 'gsap'
    }
  }
}

Everything works just fine when my project is not minified / compiled to build-version, where I end up getting this error message:

Uncaught TypeError: Cannot set property 'gsClass' of undefined

It works perfect when developing, even though it's run through an entry, main.js... Very confusing. Anyone had this problem before?

[GreenSock 8,117 Likes (Superhero)]

That is pretty weird indeed. Never heard of anything like that before. I looked at the code too and can't figure out why in the world an error like that could possibly get thrown. [scratching head] 

 

Can you provide detailed instructions about how to reproduce the issue (including what needs to be installed, where, etc.)? I don't use bower nor webpack, so I may need some hand-holding.

 

By the way, TweenMax is considered the "main" file for the "gsap" package, not TweenLite. That probably has nothing to do with these errors though. 

[OSUblake 9,990 Likes (Superhero)]

Have you tried...

externals: {
  jquery: 'window.jQuery',
  'TweenLite': 'TweenLite'
}

[Torrfura 2 Likes (Newbie)]

Hi, been busy building more and haven't had a chance to follow up on this.

I found the problem, it would be nice is someone with more webpack / node skills than me could verify.

 

It all has to do with the webpack UglifyJsPlugin, and the setting "pure_getters". When having this set to true, I get the error. There's no impact on .js size in the end, so I just removed the property.

 

But I cannot give any explanation to what lies beneath this problem.

[GreenSock 8,117 Likes (Superhero)]

For the record, GSAP 1.18.5 has some improvements for compatibility with Webpack/NPM/Browserify/Node. It was released today. You might want to give that a try. 

[heldrida 0 Likes (Newbie)]

Upgrading to Webpack 2.2 from Webpack 1 and found the same issue. Thanks for sharing the fix @Torrfura