Skip to content

Not really strict semver #15

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

Closed
phated opened this issue Jun 26, 2014 · 3 comments
Closed

Not really strict semver #15

phated opened this issue Jun 26, 2014 · 3 comments
Labels

Comments

@phated
Copy link

phated commented Jun 26, 2014

Following semver should include using dependencies that follow semver or locking in dependencies that don't follow semver. Such as https://github.com/AmpersandJS/ampersand-view/blob/master/package.json#L18. Jeremy has often stated that Underscore does not follow semver which has caused many developers time in the past. E.g. jashkenas/underscore#1684 (comment)

@latentflip
Copy link
Contributor

Great point, thanks @phated! I think we're going to take another look at lodash and figure out how to use the bits we need without too much duplication if end users also require lodash.

@HenrikJoreteg
Copy link
Member

Started a hairbrained thing (read disclaimers in readme): https://github.com/HenrikJoreteg/amp#an-idea

But wondering if maybe lodash-node is a better solution, per: AmpersandJS/amp#2

@bear bear added the question label Oct 31, 2014
@HenrikJoreteg
Copy link
Member

Cleaning up, this has been resolved for some time now as we're now using lodash individual modules for this.

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

4 participants