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

nodejs-return-status

v1.0.0

Published

NodeJS Retrun Status

Readme

nodejs-return-status

  • A simple and easy-to-use utility for returning standard HTTP responses in a Node.js application, designed for use in a MERN stack backend.

Installation


    npm nodejs-return-status

Usage

  • This package provides functions to return standard success and error responses in your Express API.

Importing the Functions

You can import the functions in your project like this:


const { ReturnSuccessMsg, ReturnResourceExists } = require('nodejs-return-status');

Functions

ReturnSuccess(res)

  • Returns only success response with HTTP status code 200

Parameters

  • res: The response object from Express.

ReturnSuccessMsg(res, msg)

  • Returns a success response with a custom message and a 200 OK status code.

Parameters

  • res: The response object from Express.
  • msg: Message that you need to send

ReturnResourceExists(res, Error)

  • Returns an error response with a 409 Conflict status code, indicating that the resource already exists.

Parameters

  • res: The response object from Express.
  • Error: Error Message that you need to send

ReturnInternalServerError(res, Error)

  • Returns an error response with a 500 Internal Server Error status code.

Parameters

  • res: The response object from Express.
  • Error: Error Message that you need to send

Example Usage


const express = require('express');
const { ReturnSuccessMsg, ReturnResourceExists } = require('nodejs-return-status');

const app = express();

// Example Route to register a user
app.post('/register', (req, res) => {
    const { email } = req.body;

    // Simulate checking if user already exists
    const userExists = email === '[email protected]';

    if (userExists) {
        return ReturnResourceExists(res, "User Already exists"); // Resource already exists
    }

    return ReturnSuccessMsg(res, "User Registered");
});

app.listen(3000, () => console.log('Server running on port 3000'));

  • Status Codes and Responses

  • 200 OK: Returned by ReturnSuccessMsg() to indicate successful operation.

  • 409 Conflict: Returned by ReturnResourceExists() to indicate a conflict (e.g., when a resource already exists).

License

This package is licensed under the MIT License

Contributing

  1. Fork the repository.
  2. Create a new branch
  3. Commit your changes
  4. Push to the branch
  5. Create a new Pull Request.

Contact