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

@micro-dev-hub/module-common-craftsman

v1.0.7

Published

A Package written by NodeJS which provide common features used in services

Downloads

8

Readme

Module-Common-Craftsman

A Package written by NodeJS which provide common features used in services

Feature

  1. Error handler for services
  2. Custom logger to monitor services
  3. Custom ESLint - ensure JS/TS code follows code conventions

How to use Module-Common-Craftsman

Error-Handler

  1. Initialize express application:
server: Express = express();
  1. Import errorHandler from @micro-dev-hub/module-common-craftsman:
import { errorHandler } from '@micro-dev-hub/module-common-craftsman';
  1. Use errorHandler in express application
express.use(errorHandler);

Note: make sure errorHandler middleware is added after routes in the express application

  1. Import and use api-response-errors

Example use validateRequest:

import express, { Request, Response } from "express";
import { body } from "express-validator";

import { validateRequest } from "@micro-dev-hub/module-common-craftsman";

const router = express.Router();

router.post(
    "/api/login",
    [
        body("username")
            .not()
            .isEmpty()
            .withMessage("Username is required"),
        body("password")
            .not()
            .isEmpty()
            .withMessage("Password is required"),
    ],
    validateRequest,
    async (req: Request, res: Response) => {
        // TODO: login logic
    }
);

export { router }

Example to use NotFoundRoutingError

import { NotFoundRoutingError } from '@micro-dev-hub/module-common-craftsman';

server.all("*",  () => {
    throw new NotFoundRoutingError();
});

Logger

  1. Import ILogger, LoggerFactory from @micro-dev-hub/module-common-craftsman
import { ILogger, LoggerFactory } from '@micro-dev-hub/module-common-craftsman';
  1. Initialize logger
const logger: ILogger = new LoggerFactory().logger;
  1. Use logger
logger.info('message');
logger.error('message');
logger.warn('massage);
logger.http('massage');
logger.debug('massage');

ESLint

  1. Add ESLint scripts to package.json
{
    "lint": "eslint --config ./node_modules/@micro-dev-hub/module-common-craftsman/.eslintrc.js './**/*.{js,ts}'",
    "lint:fix": "eslint --config ./node_modules/@micro-dev-hub/module-common-craftsman/.eslintrc.js --fix './**/*.{js,ts}'",
}
  1. Use scripts to lint application
# Analyze all ts/js files in application to find out lint error

npm run lint

# Analyze and fix lint error all ts/js files in application

npm run lint:fix

In case you want to extends/override the rules of eslint

  1. Create .eslintrc.js and extends rules of eslint from module-common-craftsman
module.exports = {
  "extends": "./node_modules/@micro-dev-hub/module-common-craftsman/.eslintrc.js",
  "rules": {
    // Add or override rules specific to your backend project
  }
}
  1. Add scripts to package.json
{
    "lint": "eslint './**/*.{js,ts}'",
    "lint:fix": "eslint --fix './**/*.{js,ts}'"
}

Note: These scripts will scan all file js, ts in your project. So if you want to ignore folder or file you can extend script with --ignore-pattern

For example, to ignore folderToExclude and its files, use:

"lint": "eslint --config ./node_modules/@micro-dev-hub/common-module-craftsman/.eslintrc.js \"./**/*.{js,ts}\" --ignore-pattern '**/folderToExclude/**'"

For example, to ignore folderToExclude and fileToExclude.ts, use:

"lint": "eslint --config ./node_modules/@micro-dev-hub/common-module-craftsman/.eslintrc.js \"./**/*.{js,ts}\" --ignore-pattern '**/folderToExclude/fileToExclude.ts'"