Search on the cheap

[smikes]

/cc @othiym23

Opening a PR against npm is premature because I still have work to do on this. Ideally the module npm-kludge-search would go away, parts being absorbed into npm and anything that doesn't need to go into npm would go to purefts or another module.

You can test out my claims and see the terrible code that backs them, though.

Building and distributing the npmdb.pft file - my suggestion would be to build nightly and have it timeout after a week, distribute by request based download. I would not expect to run the "populate" action on user machines.

[othiym23]

If npmdb.pft were built semi-regularly, it could be put behind a CDN endpoint and cached, which would make it much easier for everyone to deal with. Let me know when you have this to a place where you're comfortable with the functionality, if not yet the code. Clearly, I think this has promise!

[smikes]

Cool. Yes, distributing the Pft that way is definitely the end goal. Right now I have broken freeze (in that it does not use a zip file, and Pft is a directory) in order to work on indexing and faster result retrieval. But: soon!

[smikes]

Getting much closer. I have partial loading of values and FTS terms now implemented. Next step is to put things back into a zip file, which will mean re-asyncifying some interfaces I synced for simplicity while developing.

Not reasonable for inclusion tomorrow, but possibly next Thursday.

[smikes]

OK. Ready for some alpha testing. Who should I tap? Obviously the npm-nauts are all pretty busy, so should I ask around on Twitter or ...?

[othiym23]

Twitter, #npm on freenode, the io.js Gitter all seem like good places to canvass for testers. And yes, I am sorry I can't poke at this more directly, but my level of busyness is such that I basically have to mostly ignore my notifications for another couple weeks.

[smikes]

Those are good tips. I will give them a try. First I want to implement completion over registry packages , then I'll ask again. I've had a reasonable number of downloads so far , I'm pretty pleased. 

Remember that you're planning to (not work) more.

On Fri, Jan 30, 2015 at 5:34 PM, Forrest L Norvell
[email protected] wrote:

Twitter, #npm on freenode, the io.js Gitter all seem like good places to canvass for testers. And yes, I am sorry I can't poke at this more directly, but my level of busyness is such that I basically have to mostly ignore my notifications for another couple weeks.

Reply to this email directly or view it on GitHub:
#1 (comment)

[othiym23]

I remember that I said that, yes. ;)