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

postcss-pxv

v1.1.0

Published

Downloads

868

Readme

postcss-pxv

This plugin creates a new pixel-viewport unit of measurement called a pxv.

input:

div { width: 150pxv; }

output:

 div { width: clamp(1px, calc(150vw * (100 / var(--siteBasis))), calc(150px * var(--siteMax) / var(--siteBasis))); }

"Wow, that looks insane!" you might say. And you'd be right, but there is very good reason for it all, and we've used this very successfully on some large sites.

When to use

Use this when you want to reach for a px but need it to behave like a vw unit. Rule must support css clamp():

| ✅ Use with | ❌ Don't use with| | ----------| --------------| | width | font-size* | | height | | padding (including neg values) | | margin | | | left, right, top, bottom | | | box-shadow | | | border | |

  • Note:font-size does support clamp but responsive typography needs a different solution to allow for the browser to still be able to use the zoom functionality. (Please see the 2.0 branch alpha release of kni-scss for this.)

Harnessing the power of css custom props

By using css custom properties we can live inject a new "basis" for the scaling.

The plugin requires two custom properties:

  • --siteBasis - The size at which your layout was designed
  • --siteMax - The size at which you want you comp to stop scaling

In an example implementation you may have a site comped at 1440px, 768px, and 375px for desktop, tablet, andd mobile respectively:

:root {
    --mobile: 375;
    --tablet: 768; 
    --desktop: 1440; 
 
    --mobileMax: 600;
    --tabletMax: 900;
    --desktopMax: 1900;

    --siteBasis: var(--mobileMax); 
    --siteMax: var(--siteMaxMobile);
  }

and in a very simple implementation we can handle 95% of all responsive elements with one media query:


@media (min-width: 768px) {
  * {
    --siteBasis: var(--tablet);
    --siteMax: var(--tabletMax);
  }
}
@media (min-width: 1024px) {
  * {
    --siteBasis: var(--desktop);
    --siteMax: var(--desktopMax);
  }
}

Installation

npm i postcss-pxv --save-dev

How to contribute

for now:

  1. npm i
  2. edit index.js or input.css
  3. process css: node process-css.js