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

dansalan-microservice-common

v0.0.8

Published

Common classes and interfaces

Readme

Organization Service Microservice

Installation

$ npm install

Database

  1. Install MySQL DB
  2. Configure DB and add connection details in ['.env.dev.local', '.env.dev', '.env.prod'] whichever comes first.

Sample .env content:

DATABASE_TYPE=mysql
DATABASE_HOST=localhost
DATABASE_PORT=3306
DATABASE_USERNAME=root
DATABASE_PASSWORD=root
DATABASE_SCHEMA=OrganizationsDB
DATABASE_ENTITY_PATH=dist/**/*.entity.js
DATABASE_SYNCHRONIZE=false

set DATABASE_SYNCHRONIZE to false because we use the migration instead

Create a database schema specified in your connection details above, for example:

create database OrganizationsDB;

TypeORM Migration

Schema changes should be run in migration to ensure that the development database has the same schema as the test and production.

Execute the command below to create a new migration file. Just change <ClassName> with the migration name ie. AddCityToCountryTable.

npm run typeorm migration:create -- -n <ClassName> -d src/migrations

Alternately, you could generate a migration with the changes made in the entity folder:

npm run typeorm migration:generate -- -n <ClassName>

Running the Migrations:

  1. npm run build
  2. npm run start or start:dev

It should execute all migration scripts that are not yet executed.

Running the app

# development
$ npm run start

# watch mode
$ npm run start:dev

# production mode
$ npm run start:prod

Test

# unit tests
$ npm run test

# e2e tests
$ npm run test:e2e

# test coverage
$ npm run test:cov

Development

Create new module for an entity, for example: Role

nest g module roles

Create new controller for the Role

nest g controller roles

Create new service for the Role

nest g service roles