Josh Chisholm

http://discuss.atom.io/t/node-command-not-found/5604/2 If you open Atom from the console instead of the GUI launcher, it will have your environment variables which likely include the PATH for node.

Looks like the "npmName" is wrong here: https://github.com/cdnjs/cdnjs/pull/4626/commits/f400e3972229694e112f6fdd4322e9e969bb10f5

Looks good. Have you tested all these examples?

> quite a lot easier to understand I think the opposite personally

I think this too-many-thens problem can be solved in a general way, so I made this: https://github.com/featurist/promise-builder With this, we can transform the browser monkey API to the style above,...

Yeah, good point! Maybe there's not much difference when you factor that stuff in. The way this works in capybara is that the driver answers a query, which eventually returns...

FWIW I think a wise strategy when waiting for something to exist, is wait for the smallest piece of evidence that it exists. In the example above, I think you...

Also, you know.... perhaps the retrying isn't really browser-monkey's responsibility either 😲 ```js assert.eventuallyDeepEqual(browser.find('ul.monkey-species li').text(), [ 'Olive Baboon', 'Patas Monkey'] ) ```

Awesome idea