I looked at this module couple of weeks ago. If you check GitHub Network page here https://github.com/sgentle/phantomjs-node/network you'll see that a lot of people forked this project and add more functionality to it.
There's also another binding to Phantom: https://npmjs.org/package/node-phantom I ended up using one of the forks and declared my dependency as "phantom": "git://github.com/sebv/phantomjs-node.git" Like others suggested if you are sure that you can commit to supporting this module then follow the official dispute procedure: https://npmjs.org/doc/disputes.html Isaac said in podcast that in practice it works really well. However, If you're not sure that you'll be able to continuously devote your time to this project, then picking a decent fork may be a better idea. Andrey On Jan 1, 2013, at 23:46 , Mark Hahn wrote: > > It would be good if npm have some better procedures for that, like allow to > > retake the name, > > God forbid that we run out of names. > > > On Tue, Jan 1, 2013 at 7:20 AM, Arunoda Susiripala > <arunoda.susirip...@gmail.com> wrote: > And I would like to know that how many modules have been resolved like this? > > > On Tue, Jan 1, 2013 at 8:36 PM, Mariusz Nowak <mari...@medikoo.com> wrote: > I guess that about 50% of projects in npm reflect such state. > > It would be good if npm have some better procedures for that, like allow to > retake the name, and give rights to publish greater versions. > > On Monday, December 31, 2012 2:18:31 PM UTC+1, toranb wrote: > A few months back I took on a dependency of what appeared to be an active npm > module (phantomjs-node) > > But since then it's become clear that the maintainer is anything but. I've > even asked him to hand over the module to someone that is willing to maintain > it. But without even so much as a comment the project appears to be stuck in > limbo. > > https://github.com/sgentle/phantomjs-node/issues/57 > > The issue above was opened a month ago with no reply and I'm curious what the > community can do to help take back this well named but now dead npm module > > Thank you in advance > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > > > -- > Arunoda Susiripala > > @arunoda > https://github.com/arunoda > http://www.linkedin.com/in/arunoda > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
