npm search

[samm]

I don't understand how to use this.

I type in, for example, irc. But there is no search or go button anywhere.

If I press enter it goes to a google search results page.

I guess I have to use the command line to search.

Why bother having the web page version then?

[samm]

Actually I just found you can go here:

http://eirikb.github.com/nipster/ 

and type in, for example, irc, and then click the npm icon at the right of the result line.

It will take you back to npm site with the npm install command for that module.

[mscdex]

On Sep 23, 8:59 am, samm <sam.miller...@gmail.com> wrote:
> If I press enter it goes to a google search results page.
> I guess I have to use the command line to search.
> Why bother having the web page version then?

You can at least search by keyword using a URI like `https://npmjs.org/
browse/keyword/foo` to search for packages with the 'foo' keyword.

[Adam Crabtree]

Niice.

NPM search feels broken IMHO. Google search UI is awful in this case, esp. since most searches are looking for modules, not people, keywords, or "packages depending on", etc... and then typically my first course of action is not to read the Readme on npmjs.org, but to find the github repo and read it there where I can browse through the code easier.

Cheers,

Adam Crabtree

--
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 nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

--
Better a little with righteousness
       than much gain with injustice.
Proverbs 16:8

[Alex Kocharin]

Adam,

 

Yeah, I liked old search.npmjs.org site, but moving to google search was a mistake imho. :(

 

I'm using http://toolbox.no.de/ for that now.

--
// alex

 

 

26.09.2012, 02:34, "Adam Crabtree" <atcra...@gmail.com>:

[José F. Romaniello]

+1 It feels broken, but it will feel better if instead of redirecting to google it embeds the result in the npm page... Like my  static blog does:

http://joseoncode.com/search/?q=Node

Code 

https://github.com/jfromaniello/joseoncodecom/blob/master/search.html

[Isaac Schlueter]

The source is open. Please help. https://github.com/isaacs/npm-www

Moving to google was only a "mistake" if you'd prefer a search that
literally does nothing whatsoever, except take the registry down every
few days.

The old search.npmjs.org site used a technique that was not scalable
past a few thousand packages. At 12,000 packages, it finally was
unable to keep up with the task of building the search index, and
caused downtime and performance problems for the entire registry.
Keeping it as long as we did, that's the real mistake.

No one believes that the current search experience on the website is
ideal. But it is what we have for now. Please help with it. As much
as I'd love to spend every waking hour doing only this, I have many
other tasks to attend to.

In the meantime, the cli search is quite effective, and relatively
fast apart from the initial download of the index. But even that will
eventually fall over under the weight of Node's steadily rocket-like
increase in popularity. The only solution is to develop a good
server-side search solution that can be queried from the cli.

Microsoft has been kind enough to provide me with a free token for the
Bing API, so any solution that relies on that service would be pretty
awesome, and very easy to deploy and manage.

The source is open. Please help.

[Alex Kocharin]

Jose,

 

Are you sure you aren't violating Google's terms of service there? 

--
// alex

 

 

26.09.2012, 03:09, "José F. Romaniello" <jfroma...@gmail.com>:

[Isaac Schlueter]

By the way, in my opinion, http://www.php.net is the gold standard for
a platform/module search engine. If we can get anywhere near that
level of user-experience, then that'll be a huge win.

[José F. Romaniello]

Yes i am very sure, actually this javascript/html was generated by google when i created the custom search engine. it gave me the option to embed. Google add lots of adds in my search page  thats the trick :)

Just to make it clear, i am not sure if google is the best fit for the npm page, but i know some of you use static blog engines and this trick might he you