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

aelastics-result

v2.0.7

Published

Framework for handling results of software services

Downloads

28

Readme

AelasticS-Result

2.0.x

Framework for handling results of software services.

Getting Started

Installation: npm install aelastics-result

Description

Service is a coarse-grain functionality implemented by some piece of software (function, object method, API operation, etc.) which can be executed locally or across the network on the Cloud. It can be composed of many other sub-services.

A result of service, represented by generic ServiceResult type, can be either success (Success type) or failure (Failure type). If it is a success, then the result holds value, an outcome of the service. If it is a failure, then the result holds an array of errors (represented by ServiceError type) describing why the service was unsuccessful.

ServiceError is a logical (not actual) subtype of standard Javascript/Typescript Error class, extending it by error code property, which classifies the given error1. Failure of some complex service can be cumulative, the consequence of failures of its subordinate services. Type CummulativeError represents such situations. CummulativeError contains an array of errors which can be atomic ServiceError or again CumulativeError. Hence, complex service error scenarios can be completely described through this hierarchy of cumulative and atomic errors.

Standard Javascript/Typescript Error objects can be captured (represented by atomic ServiceError) and incorporated in this service result handling framework.

The framework maintains proper stack trace for where errors were thrown2.

1ServiceError is not actual subtype of standard javascript class Error, i.e. an instance of ServiceError`is not an instance of Error class.

2 Stack trace feature is not supported by every Javascript engine.