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

js-viewport

v0.0.4

Published

Create variables within CSS media queries that you can use to sync up your width-sensitive JavaScript methods on load and resize events.

Downloads

2

Readme

JS Viewport

Install and Bootstrap

  1. npm install js-viewport
  2. Or download the zip from GitHub
  3. Add this in your head tag: <link rel="stylesheet" href="[assetsPath]/js-viewport.css">
  4. Add this script tag: <script src="[assetsPath]/js-viewport.js" ></script>

Checkout a demo.

Basic Usage

The CSS

Basically, you set variables as generated content in the CSS. The JavaScript then reads those generated values from the page. By managing your media queries in your CSS and allowing JS to follow that lead, your presentational layer and behavioral layer are totally synced up. Another benefit is you don't have to replicate your breakpoints in your JS with matchMedia.

@media all and (min-width: 28.125em) {
  body:after {
    content: "mini";
    display: none;
  }
}

@media all and (min-width: 31.25em) {
  body:after {
    content: "tablet";
    display: none;
  }
}

@media all and (min-width: 60em) {
  body:after {
    content: "widescreen";
    display: none;
  }
}

Feel free to change the breakpoints for your own needs. You can add new ones as long as you update the types array. In the standard version, the array is located at the top of js-viewport.js. There is also an (AngularJS version)[https://github.com/MattTurnure/Viewport/tree/angular].

By the way, there is also an .scss file in there if you want to bring it into your own Sass build process.

The JavaScript

There are two methods that viewport returns: getType and watchViewport.

viewport.getType()

This method returns the generated content value set in the CSS.

console.log(viewport.getType());
// returns 'handheld', 'mini', 'tablet', or 'widescreen'

watchViewport

This method instantiates a resize event that you pass a callback to.

Example

viewport.watchViewport(function () {
    if ( viewport.getType() === 'handheld' ) {
        // doSomeHandheldThing();
    }

    if ( viewport.getType() === 'mini' ) {
        // doSomeMiniThing();
    }

    if ( viewport.getType() === 'tablet' ) {
        // doSomeTabletThing();
    }

    if ( viewport.getType() === 'widescreen' ) {
        // doSomeWidescreenThing();
    }
});