A fork of use-resize-observer that uses Motion Values from Framer Motion.
Unlike useMotionResizeObserver
, the hook will not trigger a re-render on all changes to the target element's width and / or height. Instead, it will update the height
and width
motion values. You can use these values to drive other changes to motion
components.
yarn add use-motion-resize-observer --dev
# or
npm install use-motion-resize-observer --save-dev
Note that the default builds are not polyfilled! For instructions and alternatives, see the Transpilation / Polyfilling section.
import React from "react";
import useMotionResizeObserver from "use-motion-resize-observer";
import { motion, useTransform } from "framer-motion";
const App = () => {
const { ref, width, height } = useMotionResizeObserver({
initial: { width: 100, height: 100 },
});
const background = useTransform(width, [100, 300], ["#52cb9a", "#2d8a9a"]);
return <motion.div ref={ref} style={{ background }} />;
};
You can pass in your own ref instead of using the one provided. This can be useful if you already have a ref you want to measure.
const ref = useRef(null);
const { width, height } = useMotionResizeObserver({ ref });
You can even reuse the same hook instance to measure different elements:
You can provide an onResize
callback function, which will receive the width and height of the element as numbers (not motion values) when it changes, so
that you can decide what to do with it:
import React from "react";
import useMotionResizeObserver from "use-motion-resize-observer";
const App = () => {
const { ref } = useMotionResizeObserver({
onResize: ({ width, height }) => {
// do something here.
},
});
return <div ref={ref} />;
};
On initial mount the ResizeObserver will take a little time to report on the actual size.
Until the hook receives the first measurement, it returns 0
for width
and height by default.
You can override this behaviour, which could be useful for SSR as well.
const { ref, width, height } = useMotionResizeObserver({
initial: { width: 100, height: 50 },
});
Here "width" and "height" motion values will be 100 and 50 respectively, until the ResizeObserver kicks in and reports the actual size.
If you only want real measurements (only values from the ResizeObserver without any default values), then you can just leave defaults off:
const { ref, width, height } = useMotionResizeObserver();
Here the "width" and "height" motion values will have 0
values until the ResizeObserver takes its first measurement.
const { ref, width, height } = useMotionResizeObserver();
It's possible to apply styles conditionally based on the width / height of an element using a CSS-in-JS solution, which is the basic idea behind container/element queries:
...but this is much easier with motion
elements from Framer Motion.
const { ref, width, height } = useMotionResizeObserver();
const background = useTransform(width, [100, 300], ["#52cb9a", "#2d8a9a"]);
return <motion.div ref={ref} style={{ background }} />;
The goal of Framer Motion is to allow for visual data to flow without triggering component re-renders by avoiding React's state/props. That said, if you do want to change state, you can use the onResize
callback.
const { ref, width, height } = useMotionResizeObserver({
onResize: (size) => setSize(size),
});
By default the library provides transpiled ES5 modules in CJS / ESM module formats.
Polyfilling is recommended to be done in the host app, and not within imported libraries, as that way consumers have control over the exact polyfills being used.
That said, there's a polyfilled CJS module that can be used for convenience (Not affecting globals):
import useMotionResizeObserver from "use-motion-resize-observer/polyfilled";
MIT