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

@markdomkan/wall_e

v1.0.1

Published

Errors gestor for ts/js apps

Downloads

14

Readme

Wall-e

Description

Wall-e is a exception gestor for TS/JS apps. The name is inspired by the Pixar Wall-e movie that was based on a robot that managed garbage.

Installation

yarn add @markdomkan/wall_e

Usage

  1. Register a custom error that extends from Wall_eError. This class must have message and can have 3 methods beforeAction action and afterAction. These methods all called syncronously with async/await and recibe by parameter serviceBundle object that is optional.

CustomErrors.ts

import { Wall_eError } from "wall_e";

export class CustomError extends Wall_eError {
  message = "Custom message for show at user";

  // optional
  beforeAction = async (serviceBundle: T) => {
    await serviceBundle.showErrorMessageInToast(this.message);
  };

  // optional
  action = async (serviceBundle: T) => {
    await serviceBundle.saveLogOnApi(
      `New error in user ${serviceBundle.getUser()}`
    );
  };

  // optional
  afterAction = async (serviceBundle: T) => {
    console.log("Error");
  };
}
  1. Register your custom errors and give, if you want, your serviceBundle that help you to handle errors in action hooks.

main.ts

import { registerWalle } from "wall_e";
import { CustomError } from "./CustomErrors";

// can be object, class, array... you will recive in action hooks
const serviceBundle = {
  showErrorMessageInToast: () => {
    //
  },
  saveLogOnApi: () => {
    //
  },
  getUser: () => {
    //
  },
  //
};

// order is important, if more than one function return an error, only first will be executed.
function registerErrors(walle: Wall_e) {
  walle
    .register((error: Error) => {
      if (error.message.contains("something")) {
        return new CustomError();
      }
    })
    //register function returns Wall_e object to chain register calls.
    .register((error: Error) =>
      error.networkError?.status == 401 ? new Unauthenticated() : null
    );
  //
}

const showConsoleErrorWhenCapureError = true;

registerWalle(registerErrors, serviceBundle, showConsoleErrorWhenCapureError);
  1. Use w_catch fuction to catch your errors.
import { w_catch } from "wall_e";

try {
    //
} catch (error) {
  w_catch(error);
}