Alec Larson

Now that routes and renderers are isolated, this should be pretty straight forward to add!

I don't have a machine that can run IE 11, so you're on your own. Consider providing example code that produces the same error, so others can maybe help you.

This is important for cached `` sources to emit `load` and `error` events **after** the page is hydrated. Otherwise, components will never receive them and have to resort to complex...

I'm not sure it would help ViteFlare at all to have that feature :)

Interestingly, the [ini](https://www.npmjs.com/package/ini) package has the same problem :) https://github.com/npm/ini/issues/22

If you look closer at my example, the problem is with the `[branch "v1.0"]` part :) I've worked around this by using [config-ini-parser](https://www.npmjs.com/package/config-ini-parser) instead

Any development on this issue? Will I need to manually install an older version of Chrome? Is there an easy way to tell `inspect-process` which Chrome executable to use? I'm...

Also happening with `node v7.10.1`, so maybe the version isn't relevant? I'm on macOS v10.13, using `inspect-process v0.5.0`.

Enabling logs with `node v8.9.1`, I found this information: ``` [silly] devtools: create [silly] process: listening [silly] devtools: open [silly] devtools: resize [verbose] debugger: Debugger listening on ws://127.0.0.1:9229/b92bec86-af73-446a-ab94-6cb987f8b161 For help...

Possible duplicate of #36