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

@dobert/standard-output

v2.1.4

Published

Standard Output For AWS Lambda

Downloads

57

Readme

standard-output

A. Description

Standard exit points in every functions. There are 3 types of exit point:

  • Success Response
  • Expected Error
  • Unexpected Error

B. How to use

1. Installation

npm install --save @dobert/standard-output

2. Importing

const {
    SuccessResponse,
    ExpectedError,
    UnexpectedError,
    OutputTypes,
    StatusCodes
} = require('@dobert/standard_output');

3. SET the result

SuccessResponse

const result = new SuccessResponse({
    message: 'Success to ....',
    detail: StatusCodes.REQUEST_SUCCESS,
    data: {} // data you want to binding on the response
});

Parameters description:

  • message is a simple message that you want give to the user and it must be easy to understand even by non-technical person
  • detail for success response usually is DATA_CREATED or REQUEST_SUCCESS
  • data is a information that you want to bind to the response

ExpectedError

const error = new ExpectedError();
error.additionalInfo({
    message: 'Failed to ...',
    detail: StatusCodes.UNAUTHORIZED
});

Parameters description:

  • message is a simple message that you want give to the user and it must be easy to understand even by non-technical person
  • detail for expected error usually besides DATA_CREATED and REQUEST_SUCCESS

UnexpectedError

const error = new UnexpectedError(err);

Parameters description:

  • err is from error we caught in try catch block

4. GET the processed result

result.getStandardResult();

this will return object like this

{
    code: 200,
    json: {
        message: 'Success to get data',
        data: {}
    }
}

C. Update the code SOP

  1. Change the branch

    • You must following this branch flow

      new_branch > master > release

    • Your new_branch name must start with one of these:

      • breaking-change/...
      • feature/...
      • bugfixing/...
  2. Update the version at package.json, you can refer to this versioning standard

  3. Update the CHANGELOG.md

D. How to publish the npm

  1. Login to the npm
    npm adduser
  2. publish the npm
    npm publish --access public

NB:

  • You MUST publish to npmjs only from branch release
  • If this doesn't work, please refer to npmjs documentation