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

sc-ts-bp

v1.0.3

Published

sc-ts-bp is a Scandio specific Typescript Blueprint (TODO: Generator)

Downloads

4

Readme

sc-ts-bp

sc-ts-bp is a Scandio specific Typescript Blueprint Generator

(Optional) Installation

To get the Generator:

npm i -g sc-ts-bp

Usage

To use the Generator first create an empty folder for your new Project:

mkdir newProject 
cd newProject 

then depending on if you have it installed:

generate-project 

or to directly use the Generator without installing just use npx:

npx sc-ts-bp 

Options:

| flag | description | | --- | --- | | -l, --layout | add the specified directory layout [technical, components] (default: "technical") | | -h, --help | display help for command |

This will unpack the Skeleton in the current Directory.

Possible Project Layouts

Technical Separation

% tree 
.
├── config
│   ├── custom-environment-variables.json
│   ├── default.json
│   ├── development.json
│   └── test.json
├── docker
│   └── Dockerfile
├── docker-compose.yml
├── jest.config.js
├── jest.setup.ts
├── package.json
├── package-lock.json
├── README.md
├── src
│   ├── App.ts
│   ├── controllers
│   │   └── MonitoringController.ts
│   ├── facades
│   ├── index.ts
│   ├── middlewares
│   │   └── accessLogging.ts
│   ├── repositories
│   ├── routes
│   │   └── Routes.ts
│   ├── services
│   └── util
│       └── logger.ts
├── test
│   └── monitoringRoutes.test.ts
└── tsconfig.json

Component-based Separation

 % tree
.
├── config
│   ├── custom-environment-variables.json
│   ├── default.json
│   ├── development.json
│   └── test.json
├── docker
│   └── Dockerfile
├── docker-compose.yml
├── jest.config.js
├── jest.setup.ts
├── package.json
├── package-lock.json
├── README.md
├── src
│   ├── App.ts
│   ├── components
│   │   ├── Health
│   │   │   └── index.ts
│   │   └── index.ts
│   ├── index.ts
│   ├── lib
│   │   └── logger.ts
│   ├── middleware
│   │   └── accessLogging.ts
│   └── routes
│       ├── HealthRouter.ts
│       └── index.ts
├── test
│   └── monitoringRoutes.test.ts
└── tsconfig.json

Docker

The generated Projects come with a docker-compose and a Dockerfile. Both are intended for use during ongoing development on the project.

Port '9228' is exposed for use with the debugger.

IntelliJ

Attach a Debug Configuration to the open port. Hint: Add --collectCoverage=false to jest options in the Jest Debug Template to debug tests.

VSCode

In VSCode a debugContainer can be used to directly open a VSCode Instance in Docker. VSCode will automatically prompt you to install a recommended Extension. Re-Open Workspace in Container and use VSCode as usual.

General Coding Guidelines

Where do Test files live?

| Test Type | Test File Location | | --- | --- | | Unit Tests | Beside the code files, Same file name with the .accessLogging.ts suffix | | Integration Tests | in /tests |


Future Development

OPEN TOPICS