Nathan Cahill

I think this is inevitable, Google is well known for keeping API access locked down. I don't know if debouncing is the correct answer, maybe switching to DuckDuckGo is better?

This will also allow vhtml to support arrays of JSX: nathancahill/vhtml#1, since there's nothing about JSX that imposes that restriction, it's a React implementation detail that's being fixed.

Yeah, I agree that keeping vhtml as a direct-to-string renderer is a good thing. I was already thinking about a 3 project approach, where there's room for a slightly more...

Sounds good to me. Let me take a swing at re-working this PR as a second entrypoint and see how it looks. If it feels too contrived it'll be easy...

@developit Do you have any feelings about the other PRs to work towards this goal? Deciding whether to focus my efforts on your project or a new one of my...

@leo Friendly bump to this. If there's not interest I'd be interested in maintaining a fork of the package to support this feature.

@gatherben Meanwhile you can use my fork with this feature if you'd like. Is published as `serve-proxied` on npm. Hope to see it merged some day.

@JounQin I'm not investing more time until I hear back from the maintainers that they are interested (in which case this PR can be finished) or not interested (in which...

@JounQin make sure the service running on `:8080` is expecting the URL to be prefixed with `/api/v1` and not just `/v1`

Added support for routing segments like in the `redirects` and `rewrites` options. So now it's possible to do this: ```json { "proxy": [ { "source": "/api/:object", "destination": "http://example.com/:object" } ]...