Yeah, I think we're saying the same thing regarding the placement of CustomEase being the problem. That require statement would find TweenLite. Again, removing the TweenLite dependency require statement in CustomEase would make it impossible for folks to just import CustomEase without also manually importing TweenMax or TweenLite.
That probably wouldn't happen often I guess, but it certainly could. If we switch require ". Again, this is all solved by simply putting CustomEase. Yes, people can also require eslint-config-babel without eslint and nobody expect that to work.
Without bundlers, CustomEase. Especially when they're not even part of the same package. I think you're thinking too much of outliers. With thousands of GSAP users, only a few complained. I think you're doing well. Perhaps you can outline what you support and what you don't, and setup tests for that.
If you try to support every configuration and make changes every few releases you're just playing whack-a-mole. Your current solution for CustomEase. If you don't want to remove that require, instead of distributing that commonjs-flat directory, you could have just. Plus documentation that mentions the gsap 1.
Right, but references to "TweenLite" for example wouldn't work. All the GreenSock classes themselves wouldn't be at the global scope. Code would break. It should work with a bundler because the bundler is supposed to handle the dependencies, right? So that people don't need to worry about loading whatever that particular class needs? Isn't that the point of require statements? Same with other members-only plugins. Do you see that style as pretty future-proof?
Right, which code would break? That's your code and you know how to access TweenLite globally correctly, in every case. If it's not window.
GreenSockGlobals , right? TweenLite perhaps is not a plain CustomEase dependency. What can I do with it? I'm currently using the following import import "gsap". Link to comment Share on other sites More sharing options Create an account or sign in to comment You need to be a member in order to leave a comment Create an account Sign up for a new account in our community.
Register a new account. Sign in Already have an account? Sign In Now. Share More sharing options Go to topic listing. About Converts the keyframes of the selected property in After Effects to a set of SVG path commands that can be used directly in GreenSock's CustomEase plugin Topics animation gsap curve after-effects ease keyframes greensock.
MIT License. Releases No releases published. Packages 0 No packages published. Contributors 2. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Sign up for a new account in our community. It's easy! Already have an account? Sign in here. Leaderboard More More.
Sign in to follow this Followers 9. December 5, GreenSock. Get an all-access pass to premium plugins, offers, and more! Join the Club. Iron Velvet.
0コメント