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

door-lock-project

v1.0.0

Published

RESTful API boilerplate with Typescript, TypeORM, ExpressJs & Mocha.

Downloads

4

Readme

TypeORM / Express / TypeScript RESTful API boilerplate

CI TypeScript prettier

Boilerplate with focus on best practices and painless developer experience:

  • Minimal setup that can be extended 🔧
  • Spin it up with single command 🌀
  • TypeScript first
  • RESTful APIs
  • JWT authentication with role based authorization

Requirements

Running

Easily set up a local development environment with single command!

  • clone the repo
  • npm run docker:dev 🚀

Visit localhost:4000 or if using Postman grab config.

What happened 💥

Containers created:

  • Postgres database container seeded with 💊 Breaking Bad characters in Users table (default credentials user=walter, password=white in .env file)
  • Node (v16 Alpine) container with running boilerplate RESTful API service
  • and one Node container instance to run tests locally or in CI

Features:

  • Express framework
  • TypeScript v4 codebase
  • TypeORM using Data Mapper pattern
  • Docker environment:
    • Easily start local development using Docker Compose with single command npm run docker:dev
    • Connect to different staging or production environments npm run docker:[stage|prod]
    • Ready for microservices development and deployment.
      Once API changes are made, just build and push new docker image with your favourite CI/CD tool
      docker build -t <username>/api-boilerplate:latest .
      docker push <username>/api-boilerplate:latest
    • Run unit, integration (or setup with your frontend E2E) tests as docker exec -ti be_boilerplate_test sh and npm run test
  • Contract first REST API design:
    • never break API again with HTTP responses and requests payloads using type definitions
    • Consistent schema error response. Your frontend will always know how to handle errors thrown in try...catch statements 💪
  • JWT authentication and role based authorization using custom middleware
  • Set local, stage or production environmental variables with type definitions
  • Logging with morgan
  • Unit and integration tests with Mocha and Chai
  • Linting with ESLint
  • Prettier code formatter
  • Git hooks with Husky and lint-staged
  • Automated npm & Docker dependency updates with Renovate (set to patch version only)
  • Commit messages must meet conventional commits format.
    After staging changes just run npm run commit and get instant feedback on your commit message formatting and be prompted for required fields by Commitizen

Other awesome boilerplates:

Each boilerplate comes with it's own flavor of libraries and setup, check out others:

Contributing

All contributions are welcome!