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

@eeston/grpc-create-error

v2.0.1

Published

Utility function that creates an Error suitable for gRPC responses

Downloads

1

Readme

grpc-create-error

Utility function that creates an Error suitable for gRPC responses

This forked repository aims to provide a @grpc/grpc-js compatable version of grpc-create-error. The original repository has a dependency that relies on grpc which is no longer supported.

npm version JavaScript Style Guide License

Node.js CI CodeQL

Related

grpc-error - GRPCError class that uses this module

grpc status codes - The grpc status codes.

Installation

npm install create-grpc-error --save

API

createGRPCError(message, code, metadata) ⇒ Error

Utility function that creates an Error suitable for gRPC responses. See tests for all examples

Kind: global function
Returns: Error - The new Error

| Param | Type | Description | | --- | --- | --- | | message | String | Number | Error | Object | If String the error message If Number the error code If instanceof Error, the error to source data from. We still create a new Error instance, copy data from the passed error and assign / merge the rest of arguments. This can be used to mege metadata of existing error with additional metadata. If Object, assumed to be metadata, either plain object representation or actual grpc.Metadata instance. We use grpc-create-metadata module to create metadata for the return value. | | code | Number | Object | If Number the error code If Object, assumed to be metadata, either plain object representation or actual grpc.Metadata instance. We use grpc-create-metadata module to create metadata for the return value. | | metadata | Object | The error metadata. Either plain object representation or actual grpc.Metadata instance. We use grpc-create-metadata module to create metadata for the return value. |

Example (Using standard grpc status code)

const grpc = require('grpc')
const createGRPCError = require('create-grpc-error')
const err = createGRPCError('Ouch!', grpc.status.INVALID_ARGUMENT)

Example (Custom error with metadata)

const createGRPCError = require('create-grpc-error')
const err = createGRPCError('Boom', 2000, { ERROR_CODE: 'INVALID_TOKEN' })
console.log(err.message) // 'Boom'
console.log(err.code) // 2000
console.log(err.metadata instanceof grpc.Metadata) // true
console.log(err.metadata.getMap()) // { error_code: 'INVALID_TOKEN' }

Example (Source from error and merge metadatas)

const createGRPCError = require('create-grpc-error')

const existingError = new Error('Boom')
existingError.metadata = new grpc.Metadata()
existingError.metadata.add('foo', 'bar')

const err = createGRPCError(existingError, 2000, { ERROR_CODE: 'INVALID_TOKEN' })
console.log(err.message) // 'Boom'
console.log(err.code) // 2000
console.log(err.metadata instanceof grpc.Metadata) // true
console.log(err.metadata.getMap()) // { foo: 'bar', error_code: 'INVALID_TOKEN' }

applyCreate(err, message, code, metadata) ⇒ Error

Actual function that does all the work. Same as createGRPCError but applies cretion to the existing error.

Kind: global function
Returns: Error - See createGRPCError description

| Param | Type | Description | | --- | --- | --- | | err | Error | The error to apply creation to | | message | String | Number | Error | Object | See createGRPCError description | | code | Number | Object | See createGRPCError description | | metadata | Object | See createGRPCError description |

License

Apache-2.0