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

event-response

v0.4.4

Published

Handle the results of Cloud Functions like http status code.

Downloads

15

Readme

event-response

npm version Build Status Codacy Badge License: MIT

When you use Cloud Functions's Background Functions, have you ever wanted to record success / failure respond to the client side that it succeeded?

event-response is easy to understand like success status of HTTP and can record success / failure. It is also possible to handle it on the client side using the recorded status.

Install

yarn install event-response

Overview

OK

When Cloud Functions completes successfully, call setOK().

It is 200 in http.

new EventResponse.Result(user, 'prefix').setOK()

Bad Request

When Cloud Functions fails on client side problems such as invalid parameters, call setBadRequest(). And you can set id, error.

It is 400 in http.

new EventResponse.Result(user, 'prefix').setBadRequest('error_id', 'error reason')

Inernal Error

If an error occurs on the server side, call setInternalError. And you can set id, error.

It is 500 in http.

new EventResponse.Result(user, 'prefix').setInternalError('error_id', 'error reason')

Usage

This sample is written in TypeScript.

1. Initialize

Initialize event-response in your index.ts.

import * as EventResponse from 'event-response'
import * as functions from 'firebase-functions'

EventResponse.initialize(functions.config().firebase)

2. Call set method

You can set 3 pattens.

  • OK
  • BadRequest
  • InternalError
exports.updateUser = functions.firestore.document('users/{userId}')
  .onCreate(async event => {
    if (!event.data.data().name) {
      return new EventResponse.Result(event.data.ref, 'updateUser').setBadRequest('NameNotFound', 'User.name not found')
    }

    try {
      await event.data.ref.update({name: 'new name'})
      await new EventResponse.Result(event.data.ref, 'updateUser').setOK()
    } catch (error) {
      await new EventResponse.Result(event.data.ref, 'updateUser').setInternalError('NameUpdateFailed', error.toString())
      return Promise.reject(error)
    }

    return undefined
})

The result can be got as follows.

admin.firestore().doc('user/1000').get().then(s => {
  const user = s.data())
  const status = user.updateUserResult.status
  const id = user.updateUserResult.id
  const error = user.updateUserResult.error
}

Advanced

Failure

TODO