-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package inspection #3
Comments
Perhaps just disable the "straight to github" thing now and instead go to a /module/name page where we show the relevant links to github/npm,versions,last-updated and the README.md nicely formatted? |
Yes, that could definitely work. How should we move forward on this? |
I like the idea of not going directly to the github page, and open something inline instead. Maybe still with a possibility to go to node-modules.com/module-name page so people are able to link directly to a module on the site. |
@freeall, I like the idea too. I think it's nice to be able to link to the module page as well. You could link to it on your website, and it's easy to look up a module with a known name by just typing in the URL. |
It could be awesome, if you could click to expand a given package and show the details (a bit like the npmjs.org pages, but better formatted). Maybe it's just me, but I'm usually curious to see some of the stats and find myself going to npmjs.org to find the info.
A quick implementation could just be adding a tiny link (maybe an icon or whatever, looking nice) to the corresponding page at
https://npmjs.org/package/{name}
. What do you think?The text was updated successfully, but these errors were encountered: