Alex Potsides

To ensure we can perform releases, assert dry run releases can complete successfully.

Deno as a test target

2

We support node, chromium, firefox etc as a test target: ```console $ aegir test -t node ``` ```console $ aegir test -t browser --browser firefox ``` etc We should support...

It would be really great if there was an additional step to `aegir release` that accepted a list of module names from config, generated a table of the currently installed...

Adds supports for `ipfs://` and `ipns://` URLs. - Fixes #48

Is it possible to use PromQL with Metricat? I'd like to be able to apply `rate` to a Counter but I can't seen anything obvious in the UI?

If your `tsconfig.json` has `"module": "ES2020"` or later (e.g you are outputting ESM and not CJS), TypeScript doesn't rewrite `import './foo'` to `import './foo.js'` in the transpiled output - instead...

Spec compliance?

4

I'm trying to integrate this module with some isomorphic code that runs on node and in browsers but I've noticed some incompatibilities with the WebRTC types as supplied with TypeScript...

Call callback after selecting database

1

The `select` method in the main redis client [takes a callback as it's second argument](https://github.com/mranney/node_redis/blob/master/index.js#L1004-L1017). This callback brings `redis-mock` in line with that.

fix: replace node buffers with uint8arrays

1

All use of node Buffers have been replaced with Uint8Arrays BREAKING CHANGES: - `cbor.encode` used to return a Buffer, now it returns a Uint8Array

fix: add types to exports map

1

To support the `Node16`/`NodeNext` module resolution strategy, the exports map needs a `"types"` entry for each export. Docs: https://www.typescriptlang.org/tsconfig#moduleResolution