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

release versions are using marty 0.9.17 instead of 0.10.x #11

Open
TN1ck opened this issue Jun 2, 2015 · 6 comments
Open

release versions are using marty 0.9.17 instead of 0.10.x #11

TN1ck opened this issue Jun 2, 2015 · 6 comments

Comments

@TN1ck
Copy link

TN1ck commented Jun 2, 2015

When trying to install the 0.4.0 of marty-express, npm gives this error:

npm ERR! argv "node" "/usr/local/bin/npm" "install" "marty"
npm ERR! node v0.10.35
npm ERR! npm  v2.1.18
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package marty does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer marty-express@0.4.0 wants marty@^0.9.17

@jhollingworth
Copy link
Contributor

Have you got Marty 0.9.7 installed? It got released on 26th

@TN1ck
Copy link
Author

TN1ck commented Jun 2, 2015

No, 0.10.1. I fixed with cloning marty-express and doing npm link and npm link marty-express. I don't know why the package.json is different from the one in the repository. But when you click on the commit the 0.4.0 release is reffering to, you see marty 0.9.17: https://github.com/martyjs/marty-express/blob/7f3d7a7d4925689060ab0e10ba8c6bcca53ce873/package.json

@jhollingworth
Copy link
Contributor

can you try upgrading to marty-express v0.10?

@TN1ck
Copy link
Author

TN1ck commented Jun 2, 2015

Oh I was under the impression that 0.4 is the version that supports marty 0.10.x.0.10` is working fine.

@jhollingworth
Copy link
Contributor

sadly not, v0.4 was released for Marty v0.9. I've moved version numbers of other marty repos to be in line with marty to avoid this confusion going forwards

@TN1ck
Copy link
Author

TN1ck commented Jun 2, 2015

Ah ok, Sorry then! The rapid succession of the release-dates got be thinking they are both for 0.10. This issue can be closed.

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