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

@improbable-eng/grpc-web-fake-transport

v0.15.0

Published

Fake Transport for use with @improbable-eng/grpc-web

Downloads

857

Readme

@improbable-eng/grpc-web-fake-transport

Fake Transport for use with @improbable-eng/grpc-web.

Usage

FakeTransportBuilder builds a Transport that can be configured to send preset headers, messages, and trailers for testing.

By default the Transport that FakeTranportBuilder.build() generates will trigger all of the specified response behaviours (.withHeaders(metadata), .withMessages([msgOne, msgTwo]), .withTrailers(metadata)) when the client has finished sending.

This is usually the desired flow as all of the response behaviour is triggered only after the client has finished sending as would most commonly occur in production usage.

However, in the case of bi-directional or other complex usage it can be helpful to use .withManualTrigger() to disable automatic sending of messages or headers/trailers and trigger the sending manually using sendHeaders(), sendMessages() and sendTrailers().

With Service Stubs generated by ts-protoc-gen

import { FakeTransportBuilder } from '@improbable-eng/grpc-web-fake-transport';

const fakeTransport = new FakeTransportBuilder()
  .withMessages([ new PingResponse() ])
  .build();

const client = new PingServiceClient("https://example.com", {
  transport: fakeTransport
});

client.DoPing(/* ... */);

With grpc-web

import { grpc } from '@improbable-eng/grpc-web';
import { FakeTransportBuilder } from '@improbable-eng/grpc-web-fake-transport';

const fakeTransport = new FakeTransportBuilder()
  .withMessages([ new PingResponse() ])
  .build();

grpc.invoke(PingService.DoPing, {
  host: "https://example.com",
  transport: fakeTransport,
  /* ... */
});

With withManualTrigger()

import { grpc } from '@improbable-eng/grpc-web';
import { FakeTransportBuilder } from '@improbable-eng/grpc-web-fake-transport';

const fakeTransport = new FakeTransportBuilder()
  .withManualTrigger()
  .withHeaders(new grpc.Metadata({ headerKey: "value" }))
  .withMessages([ new PingResponse() ])
  .withTrailers(new grpc.Metadata({ trailerKey: "value" }))
  .build();

grpc.invoke(PingService.DoPing, {
  host: "https://example.com",
  transport: fakeTransport,
  /* ... */
});

// Manually trigger the response behaviours
fakeTransport.sendHeaders();
fakeTransport.sendMessages();
fakeTransport.sendTrailers();

Alternatively replace the Default Transport when initialising your tests:

import { grpc } from "@improbable-eng/grpc-web";
import { NodeHttpTransport } from "@improbable-eng/grpc-web-fake-transport";

// Do this first, before you make any grpc requests!
grpc.setDefaultTransport(fakeTransport);