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
Comments
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 |
If you add the dist folder it would be possible to use the git repository as npm dependency for the moment. |
I got reply on an E-Mail:
@manifestinteractive sounds like a good solution! |
@t3easy Thanks for getting me that info. I have contacted the owner of the repo and CC'd NPM support |
@t3easy after looking back at previous releases, it looks like the 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 😄 |
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. |
This is now in the master branch. Also removed |
Hi, NPM installation fails with this log, could you please advice, thanks.
|
@allochi try |
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.
The text was updated successfully, but these errors were encountered: