Jason Miller

Likely broken by the inclusion of Array support. TBH I'm not sure if there's a better behaviour here - undefined could only really be stringified, which is super unintuitive. I'd...

Hey @aarondancer! Thanks for opening the PR. Would you be able to provide some context on why square bracket notation is important for your use-case?

Thanks for the great explanation @kevlened! This also jives with my experience. Worth noting that performance is also at play here, and reduce() has fairly poor performance.

You can already use an array key, which is better than constructing a string for offset-based access: ```js dlv(obj, ['arr', 1]) ```

Sorry for taking so long to reply here. The benchmark needs a bunch of different source objects and many variants of key in order to produce valid results. Currently since...

I believe this can be achieved via the following: ```jsx import { createContext } from 'preact'; import { useContext } from 'preact/hooks'; const HttpStatus = createContext({ code: 200 }); function...

Maybe something like this would work, as a wrapper around router? ```js import Router from 'preact-router'; import TransitionGroup from 'preact-transition-group'; const TransitionRouter = ({ children, ...props }) => { {...

Correct, it only supports one level of children. I think the only way to make this work would be to use a function-as-children approach, which is not currently supported in...

sounds awesome, looking forward to it!

One option here might be to allow passing a "wrap" function to the router. The router would pass the active child through that function, so you could consistently wrap each...