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

installable version for npm #217

Closed
t3easy opened this issue Mar 13, 2016 · 9 comments
Closed

installable version for npm #217

t3easy opened this issue Mar 13, 2016 · 9 comments
Labels

Comments

@t3easy
Copy link
Contributor

t3easy commented Mar 13, 2016

It would be nice to have an installable version as npm package without a grunt build task, because not everyone uses grunt.
Also the latest version available over npm repository is a fork with version 1.0.1.

@manifestinteractive
Copy link
Contributor

I would love to offer this via NPM. However, someone beat me to the punch on creating the NPM package and has not been keeping it up to date. Since I was not the person that submitted it, I have been unable to have it updated. I tried both contacting the person that created the NPM package itself, as well as someone within the NPM community to show I was the author.

Nothing seems to work there. If you have any advice on that, I would love to keep the NPM package up to date. But since someone else registered with the name, and has not been keeping it up to date, I am not quite sure how to work around that.

I can easily have a dist folder added to the project for no grunt requirements for those that just want to use it via NPM. But I guess getting control back of the NPM package would be a first step.

@t3easy
Copy link
Contributor Author

t3easy commented Mar 14, 2016

If you add the dist folder it would be possible to use the git repository as npm dependency for the moment.
"jqvmap": "git://github.com/manifestinteractive/jqvmap.git#v1.4.0",

@t3easy
Copy link
Contributor Author

t3easy commented Mar 15, 2016

I got reply on an E-Mail:

Hi Jan,

Thanks for emailing. In this case, we can go through the package transfer process outlined in our disputes policy:
https://docs.npmjs.com/policies/disputes#tldr

Get the author email with npm owner ls
Email the author, CC support@npmjs.com
After a few weeks, if there's no resolution, we'll sort it out.
Did you or manifestinteractive want to request ownership of jqvmap? Whoever is making the request, please go through those steps and we'll be here to help out.

Thanks so much,
Stephanie

@manifestinteractive sounds like a good solution!

@manifestinteractive
Copy link
Contributor

@t3easy Thanks for getting me that info. I have contacted the owner of the repo and CC'd NPM support

@manifestinteractive
Copy link
Contributor

@t3easy after looking back at previous releases, it looks like the dist folder has actually been apart of the repo for a while. Both the bower.json file and package.json file are also referencing the "main": "dist/jquery.vmap.min.js"

BTW, I just put out v1.5.0 if you are currently using 1.4 on a project, you might want to update to if you need fix some of the bugs mentioned in the release notes: https://github.com/manifestinteractive/jqvmap/releases

In the mean time, I guess I will leave this ticket open until we have the NPM library updated 😄

@t3easy
Copy link
Contributor Author

t3easy commented Mar 16, 2016

OK, I see. But then you should remove the post install script from the package.json. If it fails, because grunt is not installed, the jqvmap is not available under node_modules/jqvmap.

@manifestinteractive
Copy link
Contributor

This is now in the master branch. Also removed postinstall via another PR.

@allochi
Copy link

allochi commented Apr 25, 2016

Hi, NPM installation fails with this log, could you please advice, thanks.

2050 error Darwin 15.4.0
2051 error argv "/usr/local/Cellar/node/5.11.0/bin/node" "/usr/local/bin/npm" "i" "jqvmap" "--save"
2052 error node v5.11.0
2053 error npm  v3.8.6
2054 error code ELIFECYCLE
2055 error jqvmap@1.5.0 postinstall: `grunt build`
2055 error Exit status 99
2056 error Failed at the jqvmap@1.5.0 postinstall script 'grunt build'.
2056 error Make sure you have the latest version of node.js and npm installed.
2056 error If you do, this is most likely a problem with the jqvmap package,
2056 error not with npm itself.
2056 error Tell the author that this fails on your system:
2056 error     grunt build
2056 error You can get information on how to open an issue for this project with:
2056 error     npm bugs jqvmap
2056 error Or if that isn't available, you can get their info via:
2056 error     npm owner ls jqvmap
2056 error There is likely additional logging output above.
2057 verbose exit [ 1, true ]

@alex-pex
Copy link

@allochi try npm install --save github:manifestinteractive/jqvmap

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