Create hooks for @vx/responsive

We already have the HOC (and thanks for that), but what if we make it as a hook? So we can use it as: useScreenSize.

BTW, I can make the PR for that

love this idea, noting that we have discussed re-implementing the current HOCs + <ParentSize /> component to use react-use-measure.

would happily review a PR!

Alright then! I'll create the PR with this hook, using this lib!

Whenever I get to the point where I can show something, I'll post it here! Thanks!

After working on it for a bit, I think it's not worth creating it here. What we could do is add documentation to use react-use-measure. Their API is "perfect", and what I was doing was the same thing as they already did, so look at this example:

import useMeasure from 'react-use-measure'

function App() {
  const [ref, bounds] = useMeasure()

  return (
	<div ref={ref}>
		<svg width={bounds.width} height={bounds.height} />
	</div>
}

The only thing that would change from our implementation to theirs, is the way we import it, that would probably be:

import { useMeasure } from '@visx/responsive'

So what do you think of just adding this dependency to the docs?

Another alternative would be to create our own, and it would work too.

Re-thinking about it, I think we can change the implementation to something like:

<MeasureProvider>
	<Component />
</MeasureProvider>

and we can return the bounds object to the hooks, like:

const bounds = useMeasure()

And then we could simplify the usage in our case. This would simplify a lot the creation of responsive charts, as we won't need to pass the width and height down the component tree.

@williaster and @hshoff what do you guys think?

Hey @pedroapfilho 👋 . In the latest suggestion, how would the ref work with MeasureProvider? Would it render some type of element and handle all of the ref stuff?

That's an interesting thought. I do think sometimes users would want to be able to avoid rendering an additional div (or svg if you're measuring in an svg tree) and set their own ref on an element they're already rendering, so need to think more about how that might work 🤔

What this provider would do is creating the ref for the user, by himself. It could accept props to pass its own ref, but it would just for certain use-cases, that aren't that important.

The MesureProvider would do something like:

<div ref={ref}>
	<Measure.Provider value={bounds}>
		{children}
	</Measure.Provider>
</div>

Closing this as it looks like hooks were added in https://github.com/airbnb/visx/pull/1783