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

google-pubsub-mock

v1.3.0

Published

Transparently overrides @googlecloud/pub-sub for local testing

Downloads

5,655

Readme

Transparent mock for @google-cloud/pubsub

Usage

const mock = require('google-pubsub-mock')
const mockInstance = mock.setUp({
  PubSub: // the PubSub reference you're using ,
  sinonSandbox: // (optional) sinon sandbox instance you're using,
  topics: { // Topics and their subscriptions
      "topicname":{,
        subscriptions: [subscriptionName]
      }
    }
});
//publish shorthand function
mockInstance.publish(topic, message, attributes);
//helper for testing multiple delivery attempts
mockInstance.retryMostRecentPublish()

//use sinon features
mockInstance.publish.called //publish is a sinon stub
mockInstance.ack.called //ack is a sinon stub and the same one is added to all messages
mockInstance.sinonSandbox.restore() //clean up the mock, returns PubSub to its previous state.
mockInstance.clearState() //remove all state created by subscriptions and messages to avoid affecting another test suite while reusing one setup

if PubSub reference is not provided, require("@google-cloud/pubsub") is called. IF dependency versions matched and got deduplicated in node_modules, it should get the same instance, but that's generally not guaranteed (and not stable long term in my experience)

Your code might store references to the topic or subscription objects. That's why it is recommended to call setUp only once and use clearState before or after each test

Support

Supports versions 0.23.0 and above (until another breaking change. Please report an issue if you're having trouble)

Replaces PubSub key exported from the @google-cloud/pubsub package only. Direct use of other classes in there is not mocked

uses sinon stubs

Methods covered:

  • topic().publish()
  • subscribtion().on("message",...)
  • message.ack()

Other methods are not yet mocked and will run the actual implementation, which you'll notice from the errors you'd be getting form @googlecloud/pubsub