-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
define tooling #9
Comments
SWFObject does not need a JS package manager But we also need to publish the library as a package 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 |
we can also add typedoc for generating the documentation 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
The text was updated successfully, but these errors were encountered: