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-logical-fallback

v1.0.1

Published

PostCSS plugin for logical fallback props

Downloads

1

Readme

postcss-logical-fallback

This is postcss plugin for logical css props support in legacy browsers. Main idea of the plugin is an opportunity to write logical styles like in modern browsers in legacy browsers. When all of your supported browsers will support all modern logical spec you can just delete this plugin and don't rewrite your styles. Second idea of the plugin is to use logical props where they supported and do fallback only in non-supported browsers.

Main purpose of this plugin is creating fallbacks for bad supported logical props in legacy browsers. We have distinguished:

  • Absolute positioning props like inset-inline-start, inset-inline-end,inset-block-start and inset-block-end due to bad support in safari (14.1+ on desktop, 14.5+ on mobile), chrome (87+) and firefox (66+) and due to high prevalence of these props.

  • Shorthand props like inset-inline, inset-block, margin-inline, margin-block, padding-inline, padding-block due to same bad support in browsers

Full logical props support you can see here

We recommend to use this plugin with autoprefixer and setup our plugin before autoprefixer

Important Note

This plugin has been primarily designed and optimized to handle websites that support left-to-right (LTR)and right-to-left (RTL) languages. This includes languages like English, French, German (LTR), and languages like Arabic, Hebrew, Persian (RTL). Please note that the utility and functionality of this plugin may be limited when applied to websites that do not fall within these language categories.

WARNING Plugin is based on @supports at rule, so it has to be supported, see on can i use

Usage

Step 1: install plugin and postcss

npm install --save-dev postcss postcss-logical-fallback

Step 2: Find config at the root of your project: postcss.config.js, "postcss" section in package.json or postcss section in your build config.

If you haven't already use postcss you should setup it according to official documentation and add postcss-logical-fallback after it.

Step 3: Add plugin to the plugin list

module.exports = {
  plugins: [
+   require('postcss-logical-fallback'),
    require('autoprefixer')
  ]
}

Examples

Fallback for absolute positioning props

Before

.class {
  inset-block-start: 12px;
  inset-inline-end: 12px;
}

After

@supports (inset-block-start: 12px) {
  .class {
    inset-block-start: 12px;
    inset-inline-end: 12px;
  }
}

@supports not (inset-block-start: 12px) {
  .class {
    top: 12px;
    right: 12px;
  }

  [dir="rtl"] .class {
    right: 0;
    left: 12px;
  }
}

Fallback for shorthands

Before

.class {
  margin-inline: 12px;
  padding-block: 24px 36px;
}

After

.class {
  margin-inline-start: 12px;
  margin-inline-end: 12px;

  padding-block-start: 24px;
  padding-block-end: 36px;
}

Fallback for inset shorthands

Before

.class {
  inset-inline: 12px;
}

.multiple-props {
  inset-inline: 24px 36px;
}

After

@supports (inset-inline: 12px) {
    .class {
        inset-inline: 12px;
    }

    .multiple-props {
        inset-inline: 24px 36px;
    }
}

@supports not (inset-inline: 12px) {
    .class {
        left: 12px;
        right: 12px;
    }

    .multiple-props {
        left: 24px;
        right: 36px;
    }

    [dir="rtl"] .multiple-props {
        left: 36px;
        right: 24px;
    }
}