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-responsive-media-query

v1.0.1

Published

Better manage alternate layouts (like desktop/tablet/mobile) with no explicit connection between the media query details and the alternate views.

Downloads

7

Readme

Responsive Media Query Component

Better manage alternate layouts (like desktop/tablet/mobile) with no explicit connection between the media query details and the alternate views.

Example from Capital One's React web app. Responsive Component

The first component is MediaQuery. This lets you set any media queries allows you to set the media query. By default it uses just a desktop and mobile setting. When the screen resizes, the children components will render the corresponding view for that layout.

The second component, Responsive, allow you to switch between completely different views with no explicit data passed down.

Example

import {Responsive, MediaQuery} from ResponsiveMediaQuery

var App = React.createClass({
  render(){
    /* MediaQuery defaults to
      <MediaQuery query={{
          mobile:"(min-width:768px)",
          desktop:"(min-device-width:320px) and (max-width:767px)"}} > */
    return (<MediaQuery>
      <MiddleMan />
    </MediaQuery>)
  }
});

var MiddleMan = React.createClass({
  render(){
    return (<div>
      <h1>Middle Man Component</h1>
      <ResponsiveChildComponent text="Hello World" />
      </div>)
  }
})

var ResponsiveChildComponent = React.createClass({
  getDefaultProps(){
    return {text:'default'};
  },
  render(){
    const MobileView = ({text}) => (<h5>{`mobile ${text}`}</h5>);
    const DesktopView = ({text}) => (<h2>{`desktop ${text}`}</h2>);

    return <Responsive {..this.props} mobile={MobileView} desktop={DesktopView} />
  }
});

ReactDOM.render(<App />, document.querySelector('#app'));

How is works

The parent component, MediaQuery, adds a listener to window resize only once for the entire app. On mount and resize request it will check the media queries and update them only if there is a change. All the children that use the Responsive component will be trigger whenever it changes.

Advanced use

The MediaQuery component has a query prop that can be whatever media query you would like to trigger.

import {Responsive, MediaQuery} from ResponsiveMediaQuery

var App = React.createClass({
  render(){
    return (<MediaQuery query={{
              watch:"max-device-width:319px",
              mobile:"min-device-width:320px",
              table:"min-device-width:640px",
              desktop:"min-width: 1025px"}}>
      <ResponsiveChildComponent text="my title" />
    </MediaQuery>)
  }
});

var ResponsiveChildComponent = React.createClass({
  getDefaultProps(){
    return {text:'default'};
  },
  render(){
    const WatchView = ({text}) => (<span>{`watch ${text}`}</span>);
    const MobileView = ({text}) => (<h5>{`mobile ${text}`}</h5>);
    const TabletView = ({text}) => (<h4>{`tablet ${text}`}</h4>);
    const DesktopView = ({text}) => (<h2>{`desktop ${text}`}</h2>);

    return <Responsive
      {..this.props}
      watch={WatchView}
      mobile={MobileView}
      tablet={TabletView}
      desktop={DesktopView} />
  }
});

ReactDOM.render(<App />, document.querySelector('#app'));

What not to do

This is only v1. Don't mix and match multiple MediaQuery components. Just one in the app so other will pick it up. More features will be added as needed/requested.