open-index/open-npm huggingface dataset:
npm package: @stratumn/instrumentation-pg
Description: Opencensus plugin for pg
Author: Stratumn Team
Latest version: 0.2.0

# OpenCensus pg instrumentation for Node.js

This package instruments the `Client.prototype.query` and `PoolClient.prototype.query` in the [node-postgres](https://github.com/brianc/node-postgres) module. Child spans will be created anytime these methods are used when using this module.

## Usage

Add the key value pair

`plugins: { pg: '@stratumn/instrumentation-pg' }`

to your [OpenCensus](https://github.com/census-instrumentation/opencensus-node) tracing config.

Example:

```
import tracing from '@opencensus/nodejs';

tracing.start({
    samplingRate: 1,
    plugins: { pg: '@stratumn/instrumentation-pg' }
});
```

## Release process

We are using `semantic-release` to publish the package on the NPM registry. Publishing can be triggered by "promoting" a successful build on master from Semaphore UI.
The commit message summary should follow the following format:

`Tag: Message (fixes #1234)`

Where `Tag` is one of the following:

- Fix - for a bug fix. (patch)
- Update - for a backwards-compatible enhancement. (minor)
- New - implemented a new feature. (minor)
- Breaking - for a backwards-incompatible enhancement. (major)

The message summary should be a one-sentence description of the change. The issue number should be mentioned at the end. \* The commit message should say "(fixes #1234)" at the end of the description if it closes out an existing issue (replace 1234 with the issue number). If the commit doesn't completely fix the issue, then use (refs #1234) instead of (fixes #1234).

Here are some good commit message summary examples:

```

Build: Update Semaphore to only test Node 0.10 (refs #734)
Fix: Semi rule incorrectly flagging extra semicolon (fixes #840)
Upgrade: Express to 13.4.2, switch to using Express comment attachment (fixes #730)

```
npm package: @stratumn/js-chainscript
Description: Official JavaScript implementation of https://github.com/stratumn/chainscript.
Author: Stratumn Team
Latest version: 1.0.8

# JavaScript ChainScript

[![build status](https://travis-ci.org/stratumn/js-chainscript.svg?branch=master)](https://travis-ci.org/stratumn/js-chainscript)
[![codecov](https://codecov.io/gh/stratumn/js-chainscript/branch/master/graph/badge.svg)](https://codecov.io/gh/stratumn/js-chainscript)
[![Language Grade: JavaScript](https://img.shields.io/lgtm/grade/javascript/g/stratumn/js-chainscript.svg?logo=lgtm&logoWidth=18)](https://lgtm.com/projects/g/stratumn/js-chainscript/context:javascript)

Official JavaScript implementation of [ChainScript](https://github.com/stratumn/chainscript).
This is the recommended way to use ChainScript in your JavaScript projects.

## Updating ChainScript

The ChainScript definitions are imported as a `git subtree`.
Changes to the protobuf files should be done in the
[ChainScript repository](https://github.com/stratumn/chainscript).
npm package: @stratumn/media-sdk
Description: SDK for media API
Author: Stratumn
Latest version: 1.12.2

# media-sdk

SDK for the Stratumn Media API.

## Build

```bash
yarn
yarn build
```

## Usage

```typescript
import { aes } from '@stratumn/js-crypto';
import Sdk from '@stratumn/media-sdk';

const file1 = 'path/to/file1';
const file2 = 'path/to/file2';
const file3 = 'path/to/file3';
const file4 = 'path/to/file4';

const client = new Sdk('http://media-url.domain.com').setToken(
  '<stratumn_account_token>'
);

// We want to use a specific key to encrypt file1 and file2.
const encryptionKey = new aes.SymmetricKey();
console.log(encryptionKey);

const [{ digest: digest1 }, { digest: digest2 }] = await client.uploadFiles(
  [file1, file2],
  {
    key: encryptionKey.export().key
  }
);

// We let the SDK create a new symmetric key automatically for file3.
const { digest: digest3, key: encryptionKey3 } = await client.uploadFile(file3);
console.log(encryptionKey3);

// We upload file4 without encryption (it could be a user avatar for example).
const { digest: digest4 } = await client.uploadFile(file4, {
  disableEncryption: true
});

// Retrieve the file info for a single file.
const { name, download_url } = await client.getDirectDownloadInfo(digest1);
console.log(download_url);

// Download a single file.
const fileContent = await client.downloadFile(digest1);
console.log(fileContent);

// Retrieve the file info for multiple files, optionally including the
// download_url.
const files = await client.getFileInfoByDigests([digest1, digest2], true);
console.log(files);
```

## Release Process

We are using `semantic-release` to publish the package on the NPM registry. Publishing can be triggered by "promoting" a successful build on master from Semaphore UI.
The commit message summary should follow the following format:

`Tag: Message (fixes #1234)`

Where `Tag` is one of the following:

- Fix - for a bug fix. (patch)
- Update - for a backwards-compatible enhancement. (minor)
- New - implemented a new feature. (minor)
- Breaking - for a backwards-incompatible enhancement. (major)

The message summary should be a one-sentence description of the change. The issue number should be mentioned at the end. \* The commit message should say "(fixes #1234)" at the end of the description if it closes out an existing issue (replace 1234 with the issue number). If the commit doesn't completely fix the issue, then use (refs #1234) instead of (fixes #1234).

Here are some good commit message summary examples:

```text
Build: Update Semaphore to only test Node 0.10 (refs #734)
Fix: Semi rule incorrectly flagging extra semicolon (fixes #840)
Upgrade: Express to 13.4.2, switch to using Express comment attachment (fixes #730)
```
npm package: @stratumn/postgraphile-plugin-hashid
Description: PostGraphile plugin to replace database big int by hash ids
Author: Stratumn Team
Latest version: 1.0.0

[![Build Status](https://semaphoreci.com/api/v1/projects/eed6b3c3-3362-4867-a009-d11d25d72baf/2337807/shields_badge.svg)](https://semaphoreci.com/stratumn/postgraphile-plugin-hashid)
[![codecov](https://codecov.io/gh/stratumn/postgraphile-plugin-hashid/branch/master/graph/badge.svg?token=ZKGnBOIpSb)](https://codecov.io/gh/stratumn/postgraphile-plugin-hashid)

# postgraphile-plugin-hashid

This [PostGraphile](https://www.graphile.org/postgraphile/) plugin replaces database big int by hash ids

By default all Bigint are replaced by HashId.
You can avoid this behaviour for a column, input, function argument, ... using the tag `doNotUseHashId`

Examples:

```sql
comment on column foo.user_id is E'@doNotUseHashId\nThe user id type will be BigInt.';
comment on function edit_foo is E'@doNotUseHashId userId\nOnly BigInt argument userId will not be transformed.';
```

```js
export default gql`
  extend type Foo {
    """
    @doNotUseHashId
    anotherUserId type will be BigInt.
    """
    anotherUserId: BigInt!
  }
`;
```

## Install

To install node dependencies:

```bash
yarn
```

## Development

This command builds the library:

```bash
yarn build
```

## Tests

This command runs the unit tests:

```bash
yarn test
```

## Release process

We are using `semantic-release` to publish the package on the NPM registry. Publishing can be triggered by "promoting" a successful build on master from Semaphore UI.

The commit message summary should follow the following format: `Tag: Message (fixes #1234)`

Where `Tag` is one of the following:

- Fix - for a bug fix (patch).
- Update - for a backwards-compatible enhancement (minor).
- New - implemented a new feature (minor).
- Breaking - for a backwards-incompatible enhancement (major).
- Docs - changes to documentation only.
- Build - changes to build process only.
- Upgrade - for a dependency upgrade.

Rules about `Message`

- The message summary should be a one-sentence description of the change.
- First letter of the message should be uppercase.
- The issue number should be mentioned at the end.
  - The commit message should say "(fixes #1234)" at the end of the description if it closes out an existing issue (replace 1234 with the issue number).
  - If the commit doesn't completely fix the issue, then use (refs #1234) instead of (fixes #1234).

Here are some good commit message summary examples:

```
Build: Update Semaphore to only test Node 0.10 (refs #734)
Fix: Semi rule incorrectly flagging extra semicolon (fixes #840)
Upgrade: Express to 13.4.2, switch to using Express comment attachment (fixes #730)
```