npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

topicdeck

v0.1.13

Published

Web GDE Deck 💯 ========================= Inspired by River of news, but HTTPs only and a PWA.

Downloads

119

Readme

Web GDE Deck 💯

Inspired by River of news, but HTTPs only and a PWA.

Attempt to create a PWA that is a news reader that renders on the server and on the client using all the same templating and logic.

Progress

  • Client logic in SW is now shared with the Server logic [done]
  • Templating is done via streaming templates [done]
  • Use WhatWG streams in node. [done]
  • Need to clean up a lot. [errrr.....]
  • Configuration file should really be an OPML file. [todo]
  • Cache fetched data on the client and server [done]
  • To render the client it still needs JS turned on. Investigate server load of RSS feeds. [partially done]
    • This is done in the SW, will use on Server soon.

Thoughts

If possible the server logic and the client logic should be near exactly the same.

Ideally configured via a OPML file that defines the columns, that links to other OPML files that contain the feeds that should be aggregrated in this.

Thoughts:

  • The UI should render the structure without JS. Ideally after this has been rendered, I can stream in the first batch of aggreagated and merged feeds.

  • The UI should then take over and update the feeds in the client as much as possible.

  • On reload, the server should not be hit at all, save for any updates to the OPML file. In an ideal world, the SW would be doing the work.

Technical hitches: We are going to have to proxy the RSS feed requests.