open-index/open-npm huggingface dataset:
npm package: @improbable-eng/grpc-web-fake-transport
Description: Fake Transport for use with @improbable-eng/grpc-web
Latest version: 0.15.0

# @improbable-eng/grpc-web-fake-transport
> Fake Transport for use with [@improbable-eng/grpc-web](https://github.com/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 
```typescript
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
```typescript
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()`
```typescript
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:
```typescript
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);
```
npm package: @improbable-eng/grpc-web-node-http-transport
Description: Node HTTP Transport for use with @improbable-eng/grpc-web
Author: Improbable
Latest version: 0.15.0

# @improbable-eng/grpc-web-node-http-transport
Node HTTP Transport for use with [@improbable-eng/grpc-web](https://github.com/improbable-eng/grpc-web)

## Usage
When making a gRPC request, specify this transport:

```typescript
import { grpc } from '@improbable-eng/grpc-web';
import { NodeHttpTransport } from '@improbable-eng/grpc-web-node-http-transport';

grpc.invoke(MyService.DoQuery, {
  host: "https://example.com",
  transport: NodeHttpTransport(),
  /* ... */
})
```

Alternatively specify the Default Transport when your server/application bootstraps:
```typescript
import { grpc } from "@improbable-eng/grpc-web";
import { NodeHttpTransport } from "@improbable-eng/grpc-web-node-http-transport";

// Do this first, before you make any grpc requests!
grpc.setDefaultTransport(NodeHttpTransport());
```
npm package: @improbable-eng/grpc-web-react-native-transport
Description: Transport for use with @improbable-eng/grpc-web that works with React Native.
Author: Improbable
Latest version: 0.15.0

# @improbable-eng/grpc-web-react-native-transport
Transport for use with [@improbable-eng/grpc-web](https://github.com/improbable-eng/grpc-web)
that works with React Native.

## Usage
When making a gRPC request, specify this transport:

```typescript
import { grpc } from '@improbable-eng/grpc-web';
import { ReactNativeTransport } from '@improbable-eng/grpc-web-react-native-transport';

grpc.invoke(MyService.DoQuery, {
  host: "https://example.com",
  transport: ReactNativeTransport(),
  /* ... */
})
```

Alternatively specify the Default Transport when your server/application bootstraps:
```typescript
import { grpc } from '@improbable-eng/grpc-web';
import { ReactNativeTransport } from '@improbable-eng/grpc-web-react-native-transport';

// Do this first, before you make any grpc requests!
grpc.setDefaultTransport(ReactNativeTransport());
```
npm package: @improved-octo-succotash/plugin-chart-composed
Description: Superset Chart - Chart Composed
Latest version: 0.0.10

## @improved-octo-succotash/plugin-chart-composed

[![Version](https://img.shields.io/npm/v/@improved-octo-succotash/plugin-chart-composed.svg?style=flat-square)](https://img.shields.io/npm/v/@improved-octo-succotash/plugin-chart-composed.svg?style=flat-square)

This plugin provides Composed for Superset.

### Usage

Configure `key`, which can be any `string`, and register the plugin. This `key` will be used to lookup this chart throughout the app.

```js
import ComposedChartPlugin from '@improved-octo-succotash/plugin-chart-composed';

new ComposedChartPlugin()
  .configure({ key: 'nielsen-oss-composed' })
  .register();
```

Then use it via `SuperChart`. See [storybook](https://apache-superset.github.io/superset-ui/?selectedKind=plugin-chart-composed) for more details.

```js
<SuperChart
  chartType="nielsen-oss-composed"
  width={600}
  height={600}
  formData={...}
  queriesData={[{
    data: {...},
  }]}
/>
```
npm package: @improved-octo-succotash/plugin-chart-hello-world
Description: Superset Chart - Hello World
Author: Superset
Latest version: 1.1.0

## @improved-octo-succotash/plugin-chart-hello-world



This plugin provides Hello World for Superset.

### Usage

Configure `key`, which can be any `string`, and register the plugin. This `key` will be used to lookup this chart throughout the app.

```js
import HelloWorldChartPlugin from '@improved-octo-succotash/plugin-chart-hello-world';

new HelloWorldChartPlugin()
  .configure({ key: 'hello-world' })
  .register();
```

Then use it via `SuperChart`. See [storybook](https://apache-superset.github.io/superset-ui/?selectedKind=plugin-chart-hello-world) for more details.

```js
<SuperChart
  chartType="hello-world"
  width={600}
  height={600}
  formData={...}
  queriesData={[{
    data: {...},
  }]}
/>
```

### File structure generated

```
├── package.json
├── README.md
├── tsconfig.json
├── src
│   ├── HelloWorld.tsx
│   ├── images
│   │   └── thumbnail.png
│   ├── index.ts
│   ├── plugin
│   │   ├── buildQuery.ts
│   │   ├── controlPanel.ts
│   │   ├── index.ts
│   │   └── transformProps.ts
│   └── types.ts
├── test
│   └── index.test.ts
└── types
    └── external.d.ts
```