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

Bower support #1238

Closed
guybedford opened this issue Aug 5, 2014 · 2 comments
Closed

Bower support #1238

guybedford opened this issue Aug 5, 2014 · 2 comments

Comments

@guybedford
Copy link
Contributor

ESML installs with Bower, but we rely on a separate repo for this support.

Getting the releases to line up correctly is proving tricky and involves a bit of work.

I'd like to be able to offer this easy install, but in a way that is maintainable.

What are the thoughts on using TravisCI to automatically create a release archive containing just traceur.js and traceur-runtime.js that would be uploaded as the GitHub release archive associated with the version tag.

This process can be automated by following I believe - http://docs.travis-ci.com/user/deployment/releases/.

Since I've never actually done it, I'd be happy to see if I can demonstrate this workflow on a test repo first before sending a PR if it helps.

Thoughts?

@guybedford
Copy link
Contributor Author

Oh wait... Bower doesn't support doing this currently according to bower/spec#28.

Forget everything I just said.

@rayshan
Copy link

rayshan commented Aug 6, 2014

binary support is coming but may be quite a while away:
bower/registry#73

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

No branches or pull requests

2 participants