Skip to content

Conversation

@dmethvin
Copy link
Member

Is this along the lines of what you were thinking in #206 (comment) @mgol? Since we are pulling the actual dependencies from the CDN for testing, we don't actually use these npm-installed copies.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 87.5% when pulling ec6b349 on dmethvin:206-fix-deps into f7c8363 on jquery:master.

package.json Outdated
"dependencies": {
"jquery": "3.0.0"
"peerDependencies": {
"jquery": ">3.0.0"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably >= right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True, and I wonder if I should also limit to <4.0.0 since we'll plan on a new round of removals then?

@mgol
Copy link
Member

mgol commented Sep 28, 2016

Yep, I was thinking about specifying ">=3 <4". That should be enough.

Michał Gołębiowski

@coveralls
Copy link

Coverage Status

Coverage remained the same at 87.5% when pulling 2ae55f8 on dmethvin:206-fix-deps into f7c8363 on jquery:master.

@dmethvin dmethvin closed this in 5acafbc Sep 30, 2016
@dmethvin dmethvin deleted the 206-fix-deps branch September 12, 2017 19:50
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.

5 participants