Open zwetan opened 8 years ago
SWFObject does not need a JS package manager as the lib is close to the metal and have no dependencies on anything and imho should stay like that
But we also need to publish the library as a package and so should provide the different files needed by different package managers
eg. bower, node, etc.
I tend to not use bower anymore and just stick with npm, but i think we could provide both.
And for the lib dependencies itself, we may have npm-style "devDependencies" at least, event if the final lib itself does not have dependencies.
I would go with
yeah going toward the same
going with TypeScript need npm to install it so installing uglifyjs would just be another install from npm
we can also add typedoc for generating the documentation https://github.com/sebastian-lenz/typedoc
made for typescript, and install via npm
When working on a JS project usually force dev to go with a stack
SWFObject stack was
As we are "taking over" we can basically decide if we keep using this stack or change it