npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

react-media-material-ui

v3.0.1

Published

easy way to use breakpoints from your material-ui theme with react-media

Downloads

23

Readme

react-media-material-ui

Build Status Coverage Status semantic-release Commitizen friendly

An easy way to use breakpoints from your material-ui theme with (react-media)[https://github.com/ReactTraining/react-media]. This is a bit more flexible than material-ui's Hidden component because it allows you to render whatever you want if the query doesn't match, rather than just hiding the content.

This is also an especially convenient replacement for material-ui's withMobileDialog HOC:

<BreakpointMedia max="xs">
  {matches => (
    <Dialog
      fullScreen={matches}
      ...

Installation

npm install --save @material-ui/core react-media react-media-material-ui

Example

The following component will only render if the screen width is at least theme.breakpoints.values.sm (from your Material-UI theme).

import BreakpointMedia from 'react-media-material-ui/BreakpointMedia'

const HideOnMobile = ({children}) => (
  <BreakpointMedia min="sm">
    {children}
  </BreakpointMedia>
)

PropTypes

min ('xs' | 'sm' | 'md' | 'lg' | 'xl')

If given, will include minWidth: theme.breakpoints.up(props.min) in the query prop to react-media.

max ('xs' | 'sm' | 'md' | 'lg' | 'xl')

If given, will include maxWidth: theme.breakpoints.down(props.max) in the query prop to react-media.

children (((matches: boolean) => ?React.Node) | React.Node)

A function whose only argument will be a boolean flag that indicates whether the media query matches or not, returning what to render, or just a React node to be rendered if the query matches.

render (() => React.Node)

A function that is only called if the query matches, and returns what to render when the query matches.

defaultMatches (boolean)

When rendering on the server you can use this prop to set the initial state on the server to match whatever you think it will be on the client. You can detect the user's device by analyzing the user-agent string from the HTTP request in your server-side rendering code.

onChange ((matches: boolean) => any)

Callback fired when the status of the media query changes.

targetWindow (Window)

Can be specified if you want the query to be evaluated against a different window object than the one the code is running in. This can be useful for example if you are rendering part of your component tree to an iframe or a popup window.