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

are_package

v1.0.1

Published

Systematic error message and response message

Downloads

10

Readme

Systematic Response Sender with Effective Error Handle

This package is designed to handle errors effectively and streamline your try-catch blocks in the backend when sending responses.

Features

Async handler

The asynchandler file contains your async code. You can throw errors inside it using ApiError, a class designed for this purpose.

ApiResponse

ApiResponse provides a systematic response structure consisting of three elements: status code, data to be sent, and an optional message.

Here is the small example of this.

Example

import {ApiError,ApiResponse,asyncHandler} from "are_package";
const register = asyncHandler(async (req, res) => {
  
  const { fullname, email, password, username } = req.body;
 
  if ([fullname, username, email, password].some((field) => !field || field.trim() === "")) {
    throw new ApiError(400, "Please fill all the fields");
}

  let user = await User.findOne({
    $or: [{ username }, { email }],
  });
  
  if (user) {
     throw new ApiError(409, "User already exists");
  }

  const newUser = new User({
    fullname,
    username,
    email,
    password,
  });

  if(!newUser)
    throw new ApiError(500, error.message || "Some error occurred while registering");
  await newUser.save();
  res.status(201).json(
    new ApiResponse(200,newUser,"User created successfully")
  ); 
});

To handle errors in the frontend, you can use the following error handling middleware:

// Error handling middleware
app.use((err, req, res, next) => {
  if (err instanceof ApiError) {
      res.status(err.statusCode).json({
          success: false,
          message: err.message,
          errors: err.errors,
      });
  } else {
      res.status(500).json({
          success: false,
          message: "Internal Server Error",
      });
  }
});