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 🙏

© 2026 – Pkg Stats / Ryan Hefner

clean-design-tasks-ts

v1.0.0

Published

TS Clean Design practice

Readme

Practical task repository for Module 1 - Single Responsibility Principle

This repository has violations of Single Responsibility Principle, discussed in the course.
You need to identify and correct them.

General Task Guidelines

  • Please, make corrections per the principles/topics discussed so far in this course.
  • The programming language to be used is TypeScript.
  • thirdparty folder - while making changes, any files contained inside the "thirdparty" folder must not be changed. Do not modify 'thirdparty' components. These files are meant to provide context to the task and are not part of it.
  • Unit tests - they are comprehensive and mentees are free to change production code in any way until tests are green. (Use npm test to run unit tests.)
  • Modifying unit tests - mentess are allowed to modify unit tests only to make them compatible with their new, refactored API. Input and output (context and behavior / Arrange and Assert) of tests must be kept. Mentees should not refactor unit tests in the scope of the course.
  • Logic and behavior of the code must be preserved.