Club Greensock Plugins & Package / Dependency Management

[radiator]

Hi There,

 

Does anyone have a recommended workflow for using Club Greensock plugins ( e.g. MorphSVG ) alongside the NPM package within a package manager ( notably JSPM )?

 

Should one just brute force the plugins into the build and manually download/unpack/copy updates as needed?

 

Using something more manual like Grunt + Bower, this isn't as much of an issue, but moving off of bower in favor of NPM / JSPM ES6 module-based workflow, it gets a little tricky.

 

Looking for any advice to help keep the project and its dependencies nice and clean.

 

Thanks in advance for your help!

 

J

 

*Edit: similar question here: 

http://greensock.com/forums/topic/13556-how-do-i-access-pluginsother-packages-from-npm-gsap-package/?hl=es6 

 

This sorta answers my question, but searching deeper into the forums now it seems something like NPM/ES6/JSPM compatibility is a work in progress, with the special plugins having to be manually added and mapped accordingly. Will start the trial and error process....

[radiator]

Snowy, lazy Saturday night here in the northeast US. Perfect time to play around with this.

 

I think I was able to answer my own question through some trial and error. ( Moving to JSPM is a recent, major change for my agency, so the learning curve there should be taken into account in the context of my original question. )

 

This is specific to JSPM and seems to work so far, with minimal testing...

1. Create a private repo on github with my membership-only release
2. Create a private registry for that repo: https://github.com/jspm/jspm-cli/blob/master/docs/registries.md
3. Add the necessary overrides and shims into package.json as needed https://github.com/jspm/registry/wiki/Configuring-Packages-for-jspm

Still some messing around fixing errors, but shows promise.

 

Using this this method, if I get an updated release, I can commit to the private repo, tag it, and update with minimal fuss ( pending a major module-based release of course, which would negate most of this ).

 

Open to any and all tips, tricks, and knowledge bombs that may help simplify this. Being very mindful to keep our club greensock files locked down nice and tight, with the goal of being able to update projects down the road effortlessly.

 

Thanks again for reading and any assistance this forum can provide!

[radiator]

Adding to this. the above steps to create your private repo for club greensock still valid and I think useful for versioning across projects, however, there is an better answer using gsap with jspm/systemJS from a fellow member here: http://greensock.com/forums/topic/14445-tweenmax-systemjs/

 

I've added onto it if one were inclined to use that method along with a private github version of club greensock files.

 

Thanks to everyone here for having a great forum, always find it super helpful.