eirikb / nipster Goto Github PK

any domain… just something that's easier to remember/type. I have to google for this every time.

http://eirikb.github.io/nipster/#readme

Hey, if you go to page 2 and on of this search, you will see many invalid packages.

Would be great if those were excluded by nipster, as they do not even have a name field.

http://eirikb.github.io/nipster/#readme

Cheers and thanks!
D

Finding the nipster was a great surprise for me. I used the original code base and the design as base for JavaScript component search tool, now hosted at http://component.xmojmr.cz

The component dataset is smaller (only ~3000 records), but with richer column set. e.g. the tags column enables searching the dataset by a tag-cloud filter. All repositories are hosted at GitHub

I'd like to try my design against the npm-datatables.json dataset but in its present state there is not enough useful information in it

I also did not find sources of the dataset update engine mentioned in #14

Can you publish the sources or extend the dataset with more columns (as used in the component search tool)?

At this moment I'd make use of just one-time dataset, no updates needed, just to have some data for the proof of concept prototype

I just found this project today, and it seems really useful. But do you have any ideas how to automate keeping packages.json up to date automatically? The last update was 25 days ago, and I'm sure it's tedious for you to continually update it.

Perhaps a public dropbox folder, or cron job that runs and commits once a night?

sorry.. I had to say the color of the row is very hard to see.

I can't find backbone-forms in output table.

Would be great if this could be added, as then I'd be able to make links to certain searches.

Relevant line: https://github.com/eirikb/nipster/blob/gh-pages/main.js#L43

Would you be open to a pull request for this?

Thank you,
D

npm uses normalize-package-data to allow for defining a package's repository.url in a variety of ways:

{
  "repository": {
    "type": "git",
    "url": "git://github.com/npm/npm.git"
  }
}

{
  "repository": "git://github.com/npm/npm.git"
}

{
  "repository": "npm/npm"
}

These all result in repository.url being "git://github.com/npm/npm.git". Looks nipster doesn't do such normalization, so many packages (i.e. mine 😁) have a null repository in that npm-datatables.json of your's. I would've sent a PR to integrate normalize-package-data but looks like 1) backend is closed-source for the time-being and 2) it's written in C#, so one would have to port normalize-package-data.

The site is down.
I was a bit eager and wasted all my free subscription credits. Hopefully the data file is available again in some hours.

"stars" vs "stargazers" might trip those new to npmjs/GitHub

Currently only title and description are considered.

Lots of packages take great care to define proper keywords and most other searches (i.e. npm search and node-package-finder) take these into account.

After sorting by modified I see first record with 2015-05-14.
Updating has been stopped?

Automatic daily/weekly refreshes would be good, i think now it's something like 2 months old

If I search for "coffee" the first package will be "pingdom-client" which, except for the author, has the same number of forks, watchers and even links to the coffee-script page are same. "coffee-script" itself is on the second place.

This looks more a like issue of the view then an error with the search.

http://nipstr.com/#bluebird-lru-cache

In the above search result, the beginning of bluebird-lru-cache's README.md:

<a href="http://promisesaplus.com/">
    <img src="http://promisesaplus.com/assets/logo-small.png" alt="Promises/A+ logo" title="Promises/A+ 1.0 compliant" align="right" />
</a>

is being inserted into the description cell. Indeed, this HTML is the description of this module:

$ npm info bluebird-lru-cache description
 </a><img src="http://promisesaplus.com/assets/logo-small.png" alt="Promises/A+ logo" title="Promises/A+ 1.0 compliant" align="right" />

but surely some sanitation must be done, right? Couldn't this lead to XSS attacks?

When searching for git related packages, the search returns all packages on github (I think). In any case the search is not specific enough.

http://nipster.blob.core.windows.net/npm-datatables.json is missing

How about being able to sort packages by created and last updated date/times?

In order for this to be a nicer UI experience and not slow down inputting chars, nipster should debounce the filtering.
I.e. only do it once the user paused typing for 200ms or so.

Right now it filters immediately on every keystroke, causing four unnecessary searches for a, as, asy, asyn when all I wanted to see was async.

I'm on a medium-speed connection (f*k you AT&T) and 15 seconds after typing in a few characters in Nipster, there's still no result other than "Processing". I *know it will eventually return something, but other users might not.

Maybe display a larger load indicator, or some numeric progress?