Skip to content
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

Open
zwetan opened this issue Mar 16, 2016 · 5 comments
Open

define tooling #9

zwetan opened this issue Mar 16, 2016 · 5 comments
Labels

Comments

@zwetan
Copy link
Member

zwetan commented Mar 16, 2016

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

@zwetan
Copy link
Member Author

zwetan commented Mar 16, 2016

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.

@ricovitch
Copy link

I tend to not use bower anymore and just stick with npm, but i think we could provide both.

@ricovitch
Copy link

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

  • npm
  • uglifyjs

@zwetan
Copy link
Member Author

zwetan commented Mar 17, 2016

yeah going toward the same

going with TypeScript need npm to install it
so installing uglifyjs would just be another install from npm

@zwetan
Copy link
Member Author

zwetan commented Mar 18, 2016

we can also add typedoc for generating the documentation
https://github.com/sebastian-lenz/typedoc

made for typescript, and install via npm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants