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

@carpenjk/use-breakpoints

v1.0.0

Published

A library using breakpoints in react

Downloads

5

Readme

use-breakpoints

UseBreakpoints is React hook that provides values in relation to a set of breakpoints that are useful for conditionally rendering and using responsive properties when used with prop-x

Installation

  npm i @carpenjk/use-breakpoints

import

  import { useBreakpoints } from '@carpenjk/use-breakpoints

Usage

The useBreakpoints hooks provides access to the breakpoints and related functions and calculated values. It is useful for client side only code that needs to evaluate properties indexed by breakpoints.

const breakpoints: {
    0: 0,
    1: 880,
    2: 1050,
    3: 1200,
    4: 1400,
  }

const br = useBreakpoints(breakpoints);

// assume current window.innerWidth = 1000
//br = 
// {
//   br: [0, 880 , 1050, 1200, 1400],
//   upper: 1050,
//   lower: 880,
//   indexofLower: 1,
//   ratio: 0.838, //(1- (upper - lower) / upper)
//   current: {
//      width: 1000
//      height: 1080
//    }

    // br =
      //new breakpoint object with numerical pixel values
    //   br: {
    //     0: 0,
    //     1: 400,
    //     2: 800,
    //     3: 1200
    //   },
    //   //original breakpoint object
    //   breakpoints: {
    //     0: 0,
    //     1: 880,
    //     2: 1050,
    //     3: 1200,
    //     4: 1400,
    //   },
    //   upper: 1050, 
    //   lower: 880,
    //   indexOfLower: "0",
    //   ratio: 0.838 //1 - (upper - lower) / upper  // in consideration for future intellegent br functionality
    //   current: { width: 1000, height: 1080 },  // window.innerWidth && window.innerHeight
    //   toArray: expect.any(Function)  //array of breakpoints sorted ascendingly
    // });

// }

const indexedPropVal = getIndexedPropValue([100, 200, 300], br.indexOfLower);
// indexedPropVal = 200;

//conditional rendering can be done comparing sizes or with index of lower
if(br.current.width > br.br["2"]){
  return (<SomeComponent>)
}

if(br.indexOfLower = br.br["2"]){
  return (<SomeComponent>)
}

Breakpoint Keys

Due to the way native javascript functionality is defined, breakpoint keys must all appear to be numerical to the javascript compiler or can be alpha-numeric defined in ascending order

  //this is fine
  const breakpoints: {
    0: 0,
    1: 880,
    2: 1050,
    3: 1200,
    4: 1400,
  }

//this is fine
  const breakpoints: {
    zero: 0,
    sm: 880,
    md: 1050,
    lg: 1200,
    xl: 1400,
  }

// this is not ok  (edit: this may be ok because the numerical-like key is the first defined)
    const breakpoints: {
    0: 0,
    sm: 880,
    md: 1050,
    lg: 1200,
    xl: 1400,
  }