-
Notifications
You must be signed in to change notification settings - Fork 65
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
Installing v2.0.6 via NPM installs v2.0.4 #40
Comments
Hi there, I had the same issue before and it was fixed. (#34) Apparently for some reason it is back. For the mean time Cheers, |
Hello, Any ideas? Did it et fixed for you? Cheers, |
Hey @dorukeker, I was using a Mac when I was running into this issue. Running on Node v6 NPM v3. I've not checked on another machine yet to see if it's consistent. I will try to do that soon for you to see if I can repeat the issue. |
Hi there! For now i've reverted to using the github repo url, eg: |
Hi There, I had a long email traffic with NPM about this. We tried to clear the npm cache etc. For now I can think of two options:
Hope this helps. |
Nps - should be fine for now. BTW, unrelated - but thank you from the bottom of my heart, for making this available on npm and in MIT. Having to use bower just for fulltilt was killing me. :P |
@glomotion I am glad you find it useful. :) |
Hello, Cheers, |
I've just tried installing this library via NPM and both
npm install gyronorm -S
andnpm install [email protected] -S
are installing the library, and adding v2.0.6 as the dependency in package.json file, but the code downloaded and in the node_modules folder is the code for v2.0.4.I've managed a workaround by adding this as the dependency in my package.json
Can someone else try installing v2.0.6 via NPM and check the node_module folder to confirm this is an issue?
Thanks
The text was updated successfully, but these errors were encountered: