hyperdrive-daemon-client icon indicating copy to clipboard operation
hyperdrive-daemon-client copied to clipboard

A client library and CLI tool for interacting with the Hyperdrive daemon.

Results 12 hyperdrive-daemon-client issues
Sort by recently updated
recently updated
newest added

Adds common methods to the output of the stat() call: - isSocket - isSymbolicLink - isFile - isBlockDevice - isDirectory - isCharacterDevice - isFIFO These functions were included in the...

_WIP._ This PR should move the `import/export` commands to the `client.drive` interface. Added some tests on the hyperdrive-daemon ends.

**Describe the bug** Method calls from a `Hyperdrive` instance hang indefinitely if the Hyperdrive Daemon was stopped or crashed. Because the `HyperdriveClient` is **To Reproduce** Node REPL with `--experimental-repl-await` flag...

**Describe the bug** After initializing the client, the `client.drive` is null. **To Reproduce** ``` const { HyperdriveClient } = require('hyperdrive-daemon-client') // found under ~/.hyperdrive/config.json const client = new HyperdriveClient('localhost:3101', 'your_access_token')...

To visualize the current state of the daemon and any further changes in a desktop app, it would be good to have a stream one could subscribe to that would...

The `writeFile()` method needs to accept an `opts` param, which I believe is the exact same as the `createWriteStream()` method. AFAICT this will require updating the wire proto because the...

I found that if a `createWriteStream()` call was creating an error, the error wasn't getting pushed into the writestream. (I'm not 100% sure where the error was occurring, possibly in...

When I log the .value.stat of an entry emitted by `createDiffStream()` I get this: ```js { wrappers_: { '11': [Object] }, messageId_: undefined, arrayIndexOffset_: -1, array: [ 33188, 0, 0,...