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

generic-response

v3.0.1

Published

A package for generating standardized and pretty HTTP responses.

Downloads

25

Readme

Generic Response

This module provides a set of functions for generating standardized HTTP responses for various scenarios in web development. These responses are designed to streamline the handling of common HTTP status codes and simplify the process of crafting consistent responses across different parts of an application.

Installation

npm install generic-response
const { okResponse } = require('generic-response');

const getAllUsers = async (req, res) => {
  try {
    const users = await prisma.user.findMany();

    const response = okResponse(users, "Users retrieved successfully.");
    return res.status(response.status.code).json(response);
  } catch (error) {
    const response = serverErrorResponse(error.message);
    return res.status(response.status.code).json(response);
  }
};

// Example response

{
  "status": {
    "code": 200,
    "success": true
  },
  "data": [
    {
      "id": 1,
      "name": "John Doe",
      "email": "[email protected]"
    },
    // More user objects if available
  ],
  "error": null,
  "message": "Users retrieved successfully."
}

Available Functions

  • okResponse(data, message): Returns a successful response with a status code of 200.
  • createSuccessResponse(data, message): Returns a successful response for a resource creation operation (status code 201).
  • updateSuccessResponse(data, message): Returns a successful response for a resource update operation (status code 200).
  • deleteSuccessResponse(data, message): Returns a successful response for a resource deletion operation (status code 200).
  • emptyResponse(): Returns an empty response with a status code of 204.
  • badRequestResponse(message): Returns a response indicating a client error with a status code of 400.
  • unauthorizedResponse(message): Returns a response indicating authentication failure with a status code of 401.
  • forbiddenResponse(message): Returns a response indicating insufficient permissions with a status code of 403.
  • notFoundResponse(message): Returns a response indicating that the requested resource was not found with a status code of 404.
  • conflictErrorResponse(message): Returns a response indicating a conflict with the current state of the server with a status code of 409.
  • tooManyRequestsResponse(message): Returns a response indicating that the client has sent too many requests in a given amount of time with a status code of 429.
  • serverErrorResponse(message): Returns a response indicating an internal server error with a status code of 500.
  • genericResponse(statusCode, data, message): Returns a generic response with the specified status code, data, and message.