npm package discovery and stats viewer.
[free text search, go nuts!]
pkg:[package-name]
@[username]
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.
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.
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 🙏
next / express / next-routes
redux / react-redux / next-redux-wrapper / redux-thunk / redux-logger
babel-plugin-module-resolver / babel-plugin-styled-components
© 2026 – Pkg Stats / Ryan Hefner
A transfer layer repository based on ddd and axios.
Reskill 是一个基于axios、ddd思想进行设计的前端请求层框架。
自从半年前我开始接触ddd思想，就被它深深的吸引了，ddd指引我思考了很多东西。
这些东西大致可以倾向于以下几点：
不论技术还是架构、最终都是为业务服务的
在传统开发的过程中，我们经常丢失了一些原本属于业务的点（例如业务中用例行为的语义特点）
不论是前端还是后端，都是基于业务所分析出来的模型，在其基础之上进行开发的，因此模型是本源，是最重要的东西
在一切设计都进行的很理想的前提下，前后端的数据传输模型（即dto）变化的可能性不大，因此它不应该成为系统维护的痛点
基于以上几点，我又产生了如下思考：
如何利用好typescript的特性，让请求层面的代码提示更加友好
能否将请求层与模型层合并并抽象成单独的一层，store只负责调用
后端dto发生变更时，如何降低前端的维护难度
