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

shorthand-edge-omissions-stylus

v0.1.3

Published

Allow omitted values in shorthand 1-value, 2-value, 3-value, 4-value padding and margin.

Downloads

3

Readme

Shorthand Omissions for Stylus

Build Status

Allow omitted values in shorthand 1-value, 2-value, 3-value, 4-value padding and margin.

.
.
.

Install

npm install git://github.com/jasonkuhrt/better-clockhand-stylus.git --save

Then in your stylus compile function

...
stylus.use(require('better-clockhand-stylus')())
stylus.import('shorthand-edge-omissions')
...

Or in your stylus CLI command

stylus ... --import ./node_modules/better-clockhand-stylus

.
.
.

Examples

2-value

.foo-selector
  padding 4rem _
.foot-selector {
  padding-top   : 4rem;
  padding-bottom: 4rem;
}

.
4-value

.foo-selector
  padding 4rem 4rem _ 4rem
.foot-selector {
  padding-top  : 4rem;
  padding-right: 4rem;
  padding-left : 4rem;
}

.
.
.

What

With omissions you never have to leave shorthand margin/padding syntax. CSS often forces you to leave shorthand even if you'd prefer not to. For instance you cannot specify just margin-top/margin-bottom.

Native CSS padding/margin shorthand syntax vs omissions:

.foo { margin : 4px 0; }    .foo { padding: 0 25px 46px; }    .foo { padding: 4px 0 0 17px; }
.foo { margin : 4px _; }    .foo { padding: _ 25px 46px; }    .foo { padding: 4px _ _ 17px; }

Omissions allow you to skip values, whereas CSS forces you to assign something.

.
.
.

Why

  • It makes writing your CSS more fun
  • Collecting all padding or margin side properties (top/right/bottom/left) on one line helps readers visually scan for dimensions information.
  • In my experience writing CSS can be a verbose, repetitive, and fatiguing experience; small effecientcy wins like ommissions will eventually make the load noticably lighter
  • Writing margin: 4px 0 0 17px; when you don't actually need those zeros is error-prone, especially when using modern OOCSS patterns that break styling across discrete classes because 0 on a generic class might blow away an actually meaningful unit on another generic class. It is also a diservice to readers and logic to provide meaningless data for the sake of shorthand syntax.

.
.
.

License

MIT

Further Reading

Learn more about CSS shorthand: https://developer.mozilla.org/en-US/docs/CSS/Shorthand_properties