Matthew Turney

This is probably superseded by #138

This is a mission critical bug as it renders this cookbook unusable with Berkshelf. What is holding it back from a merge?

I'm getting the same results as the OP. I even tried previous versions of `inspect-process` and it still breaks with the same results. A Chrome window opens with the url...

``` ╭─mturney@mturney-laptop ~/Workspace/waybetter/wb-admin ‹ruby-2.3.3› ‹7.5.0› ‹master*› ╰─➤ inspect --log-level=silly node_modules/ava/profile.js app/components/Header/index.test.js 1 ↵ sill devtools: create sill process: listening sill devtools: open sill devtools: resize verb debugger: Debugger listening on...

It seems putting the URL manually in Chrome works fine. It's just the auto open that breaks. Could be an extension issue?

I reinstalled `inspect-process` with the exact same result.

Not sure I like that. But clear documentation on the limitation would be nice. There are many reasons why you might want to be using the beta or canary versions...

@jaridmargolin I forgot that this is _just_ for the inspector. I'm on board with that idea, especially a selection option for multiple Chrome versions. I think it's important not to...

This is completely blocking for server side rendered apps. What is the recommended workaround? Could the global be mocked just so the import works on the server?

As a workaround I'm lazy loading the branch library using `import()`. Another option may be to mock the global `window` and `navigator` server side but that could get messy.