This React hook makes it easy for you to match with your media queries. Be it window or any container element!
Get it: npm install react-use-queries --save
tiny ✔️ efficient ✔️ fast ✔️ powerful ✔️ cross-browser ✔️
dependencies ❌ polyfills ❌ ResizeObserver ❌
Given things you want to do with your media queries you can ask for a list of things that match!
const queries = {
'(max-width: 299px)': { thing: 'A' },
'(min-width: 300px) and (max-width: 599px)': { thing: 'B' },
'(min-width: 600px)': { thing: 'C' }
}
function ResponsiveComponent() {
const [things] = useQueries(queries, global)
// server side: = []
// client side: = [{ thing: 'A' }]
// or: = [{ thing: 'B' }]
// or: = [{ thing: 'C' }]
return (
<div>
Things that match:
<pre>{JSON.stringify(things, null, 4)}</pre>
</div>
)
}The global there is actually window, but Babel handles global so that both server and client side code can work!
You can use window if you're dealing with client-only codebase (and don't have anything to fix global for you).
In this case you can omit use of the second parameter, but you must then place a mediaQueryListener element inside a container element.
import React, { useMemo } from 'react'
import useQueries from 'react-use-queries'
// define this outside component to keep the same reference
// or if you need this to be dynamic: useMemo
const queries = {
'(max-width: 299px)': 'small',
'(min-width: 300px) and (max-width: 599px)': 'medium',
'(min-width: 600px)': 'large'
}
const positionRelative = { position: relative }
function ResponsiveComponent() {
const [[size = 'default'], mediaQueryListener] = useQueries(queries)
// for demo purposes set a width that is smaller than the viewport width
const style = useMemo(() => ({ width: '50%', ...positionRelative }), [positionRelative])
return (
<div style={style}>
{mediaQueryListener}
<h2>Size is <code>{size}</code></h2>
</div>
)
}mediaQueryListener is a single <iframe src="about:blank" /> element.
For the media queries (or container queries) to work on elements you must give a containing element a style that is not
static (or initial). Most commonly this means applying position: relative;. This is required, because a
trick originating from 2013 used for element resize detection is used here in a modern
flavor, but instead of detecting resize we use matchMedia instead. The mediaQueryListener element is an <iframe />
with url set to about:blank. Then this iframe element is sized to full size of it's parent by absolute positioning,
hence requirement for position other than static.
All current container query solutions have issues with circularity: react-use-queries does nothing to protect against these, so you should always make sure your styles don't cause unintended side-effects. For example, changing parent element's border can change it's size which can then result to infinite resize loop as each style changes the content size. Also, parent element's size shouldn't be determined by it's children's size.
You know how annoying it is to control element sizes via media queries in CSS? Well, I hadn't found out about container
queries until just recently (around November 2019) and ended up reading and researching a lot on the topic. Also, I
think I got a pretty unique idea using matchMedia of the about:blank page instead of resize events. Another idea was
to output array of matches, which I think is both clever and simple way to create a powerful hook for all sorts of media
and container query needs.
I used the excellent react-resize-aware as an inspiration for the
minimal bundle size. Thanks to the author of that hook! Previusly I did some work creating
use-element-query, but it uses DOM mutations outside React and also has
a bit sloppier API. I ended up putting more effort into polishing this hook and even choosing a much better name.
- CSS Element Queries: type
[min-width~="size"]to CSS - CQ Prolyfill: write
:containerpseudo-selectors to your CSS - EQCSS: use
@elementqueries in your CSS container-query: lets you have@containerqueriesreact-measure: get all sorts of measurements of an elementstyled-container-query: write:containerwith Styled Components
And finally, I recommend react-resize-aware if you need to know
about element resizing and don't want to use ResizeObserver due to current state of browser support!