After creating a client, drive is null

[RnbWd]

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')
// or 
const client = new HyperdriveClient()

console.log(client)
client MainClient {
  endpoint: 'localhost:3101',
  token: '0ffba7a618e39c59ad76d943033c05ff6692c491f248bd3451dd633f01e59418d3cd3c5a7d7e2f18cf53fec7050bd652e54b28fb606575555127ae91ae795d65',
  opts: {},
  fuse: null,
  drive: null,
  peersockets: null,
  debug: null,
  peers: null,
  _client: null,
  _readyOnce: null,
  ready: [Function (anonymous)]
}

const drive = await client.drive.get()
// throws error

Expected Behavior What did you expect to happen?

** OS ** macOS

** Node version ** 13.4

** Was the daemon installed from NPM or bundled with Beaker? ** npm

Add any other context about the problem here.

Important Note: Daemon errors are likely to be found in ~/.hyperdrive/log.json or ~/.hyperdrive/output.log (the latter is for unexpected, non-JSON output). These files might contain sensitive drive keys, so don't upload the whole thing -- just extract any stack traces or odd error messages!

[metanomial]

The HyperdriveClient.drive namespace, and others, is null until HyperdriveClient.ready() is called and resolves. The details of this operation should be properly documented.