Allow typeahead bower install to succeed against jquery 2+

[wbbradley]

I don't see anything in typeahead that prevents its use on higher versions of jQuery.

[wbbradley]

Hmm... back to the drawing board.

[jharding]

The unit test suite failed cause the location of the jQuery file in the 1.7 distribution is different from the location in 2.x distribution.

And you're correct, >= 1.7 should be the requirement.

[wbbradley]

@jharding Do you have any quick pointers to how I might fix the issue you mentioned? I'm not super familiar with the config for this project.

[cedrichan]

Is it not sufficient to revert commit 6dbc2be?

[cedrichan]

See #905

[jharding]

I'm dumb. What I should have done is left "jquery": ">=1.7" as a dependency and then added "jquery": "~1.7" as a dev dependency.

[cedrichan]

Wouldn't that just install the latest jquery anyway, since it would install what's specified in dependencies over devDependencies?

[jharding]

Wouldn't that just install the latest jquery anyway, since it would install what's specified in dependencies over devDependencies?

Based on what I know, devDependencies will get precedence over dependencies unless the --production flag is used during install.

[jugglinmike]

@jharding I just tried to put together a new pull request based on your request. Unfortunately, it looks like Bower does not give precedence to devDependencies--when dependencies and devDependencies describe a Bower component at two different versions, Bower honors the version in dependencies.

I think a complete solution will entail more infrastructural work: the tests should run against all supported versions of jQuery. In the immediate term, though, it might make sense to merge gh-905 since this is causing problems for people today.

[jugglinmike]

@jharding Actually, I found a short-term solution that should make everyone happy: #924

[jharding]

@jharding I just tried to put together a new pull request based on your request. Unfortunately, it looks like Bower does not give precedence to devDependencies--when dependencies and devDependencies describe a Bower component at two different versions, Bower honors the version in dependencies.

Hmm, when I played around with it, bower was giving precedence to devDependencies. Can you try out #917 and let me know if that doesn't work for you?

[jugglinmike]

That branch seems to work fine. Not sure what I was doing differently, but I guess the implicit solution should be fine.