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

Fixes for bower.json #40

Merged
merged 1 commit into from May 13, 2013
Merged

Fixes for bower.json #40

merged 1 commit into from May 13, 2013

Conversation

pdf
Copy link
Contributor

@pdf pdf commented May 13, 2013

  • Fix jquery dependency
  • Include all production files in main
  • Ignore everything else

Refs #39

I'm pretty new to all this JS packaging stuff, but it seems like currently people tend to maintain two repositories for dealing with bower, with a bower-specific repository that contains only the built version and a bower.json. That seems like a whole lot of wasted effort, so I don't know if you want to go that far, hopefully that gets resolved after the bower rewrite is finished. For now I've just fixed made the above changes so that it works - though files are still deployed to messenger/build/(js|css) - and doesn't ship all the extra stuff like libs and source. All in all, bower still seems a little confused about what main is actually meant to be currently, so, I've just made sure it references everything required.

I don't know if this is expected to work with JQuery 2.0.0, but if not, it might also be worth adding a dependency restriction to ~1.9.1

- Fix jquery dependency
- Include all production files in `main`
- Ignore everything else
zackbloom added a commit that referenced this pull request May 13, 2013
@zackbloom zackbloom merged commit b30546a into HubSpot:master May 13, 2013
@zackbloom
Copy link
Contributor

Works for me, thanks @pdf.

@zackbloom
Copy link
Contributor

We will have to conduct an inventory of exactly which versions of jQuery are supported. I added an issue to fix whatever causes problems on 2.0.0.

@pdf
Copy link
Contributor Author

pdf commented May 13, 2013

Is it possible to retag or bump the version? It's sadly required until the bower rewrite introduces git ref support.

@zackbloom
Copy link
Contributor

I just pushed v 1.3.1, let me know if that is not what you need.

@pdf
Copy link
Contributor Author

pdf commented May 15, 2013

The 1.3.1 tag somehow seems to have picked up the old bower.json?

https://github.com/HubSpot/messenger/blob/3c392d37e12ec113dcf7c25b1886fea95f0a7d4d/bower.json

@zackbloom
Copy link
Contributor

Ah, yea. Would a 1.3.1a release help?

@pdf
Copy link
Contributor Author

pdf commented May 16, 2013

Sadly, that's not semver, so I think bower will barf :-(

@zackbloom
Copy link
Contributor

Ah yea, and 1.3.1-a would compare lower than 1.3.1. I'll try and get 1.3.2 out in the next day or so.

@pdf
Copy link
Contributor Author

pdf commented May 17, 2013

No worries, thanks Zack

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

Successfully merging this pull request may close these issues.

None yet

2 participants