NullVoxPopuli

Resolved the comments since none of the original code from my first pass exists anymore

looks like `lint:git` is failing on commits that precede my own.

Is that the same as awaiting at the call site? https://github.com/NullVoxPopuli/emberclear/pull/279/files#diff-06c4d850dcc0e9d111008e627c52f949R48 ```ts let [aInviteUrl, bInviteUrl] = await Promise.all([ a.addFriend.inviteUrl, b.addFriend.inviteUrl, ]); ```

doh. anywho, _the plot thickens_. I did: `pageObject.isExisting().then(console.log)` and got `true`. :-\ however, the return value of the attribute is still undefined:  Just added some more console logs: ```...

the value exists: 

Looks like https://superuser.com/a/1036062

How do you forward browser args?

The answer: create a new file containing: ```ts const chai = require('chai'); const chaiWebDriver = require('@faltest/chai'); chai.use(chaiWebDriver); // provides page object apis chai.use(require('chai-string')); chai.use(require('chai-fs')); chai.use(require('chai-as-promised')); // provides "eventually" module.exports =...

Based on this: https://github.com/giggio/node-chromedriver/blob/master/README.md#custom-binaries-url I wonder if I should force a new install of chrome driver each run and somehow ignore the bundled one?

Or maybe I could use selenium instead of browser specific drivers? https://github.com/giggio/node-chromedriver/blob/master/README.md#running-with-selenium-webdriver Hmm