Strange version 0.0.0 in package.json #40

Activity

1. melanke commented on Mar 27, 2013

   

   melanke

   on Mar 27, 2013

   Owner

   More actions

   Well, I am not the mainteiner of WatchJS on NPM. Sadly @mappum dont answer my request. And I am not used to package.json

   but if you say I have to change the version to 1.3.0 I will do it soon.

   Thanks for your feedback ;)
2. mappum commented on Mar 27, 2013

   

   mappum

   on Mar 27, 2013

   Contributor

   More actions

   Sorry, I can fix that. Also, @melanke I tried to add you to the npm package but for some reason it always fails.
3. synaptiko commented on Mar 27, 2013

   

   synaptiko

   on Mar 27, 2013

   Author

   More actions

   Ok, it would be great and installing to the NMP repository would be the best because now it's not installing the newest (current) version.
4. melanke commented on Mar 27, 2013

   

   melanke

   on Mar 27, 2013

   Owner

   More actions

   @mappum maybe the only way is deleting this npm package and then I create an official
5. nfleury commented on Jan 6, 2015

   

   nfleury

   on Jan 6, 2015

   More actions

   @melanke @mappum , obviously the problem was not fixed and this is blocking those who want to use this nice library with nodejs. Any update about this ?

   👍React with 👍1Reacted by David Kudera
6. nopnop commented on Jun 12, 2015

   

   nopnop

   on Jun 12, 2015

   More actions

   @nfleury Hardly a good solution but you can do npm install --save git+https://github.com/melanke/Watch.JS.git

   @mappum : Bump !

   • @melanke suggested to delete the package.
   • Please read https://docs.npmjs.com/misc/disputes
   • Or, at least, until the resolution of this issue, publish on npm, because this is too confusing (didn't you took the responsibility here: Added to npm #32 ?)
   • Related to npm watch.js is out of date, silently breaks on examples #54 Infinite loop on pushing to array #67 clerical error on user-content-do-you-want-to-know-when-new-attributes-change-too ? #87