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

mission-completed

v0.1.10

Published

Stop processing even if Cloud Functions fires multiple times.

Downloads

6

Readme

mission-completed

npm version Build Status Codacy Badge License: MIT

Note: Trigger events are delivered at least once, which means that rarely, spurious duplicates may occur. https://cloud.google.com/functions/docs/concepts/events-triggers#triggers

Cloud Functions rarely fire multiple times. If multiple payment occurs, it is a big problem!!

mission-completed uses transactions to prevent multiple trigger events.

If you try to set the completed flag to true many times, CompletedError will be returned.

await Mission.markCompleted(ref, id) // first: success
await Mission.markCompleted(ref, id) // second: throw CompletedError

Results are saved like this.

Install

yarn install mission-completed

Usage

This sample is written in TypeScript.

1. Initialize

Initialize event-response in your index.ts.

import * as Mission from 'mission-completed'
import * as functions from 'firebase-functions'

Mission.initialize(functions.config().firebase)

2. mark completed in Cloud Functions

If mission has already been completed, throw CompletedError in Mission.markCompleted(event.data.ref, 'updateUser').

exports.updateUser = functions.firestore.document('users/{userId}')
  .onCreate(async event => {
    try {
      await Mission.markCompleted(event.data.ref, 'updateUser')
    } catch (error) {
      if (error.constructor === Mission.CompletedError) {
        console.error(error, 'Mission has already been completed.')
        return Promise.reject(error)
      }
    }

    await event.data.ref.update({updated: true})

    return undefined
})

This will continue the initial process, but the simultaneous firing process will stop with CompletedError.

License

MIT