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

@streetstrider/axiom

v1.0.3

Published

Axiomatic LESS/CSS mixins

Downloads

5

Readme

axiom

npm|@streetstrider/axiom ISC licensed

Axiom is a set of axiomatic CSS mixins.

the idea

1: Consider the following CSS property name and property value domains.

| key | value | | --- | --- | | display | block | | | flex | | | inline-block | | | inline | | position | relative | | | absolute | | | fixed | | font-weight | bold | | font-style | italic | | … etc ||

In many cases, the value itself is representative enough and even unique across all property domains. When you see value like block it is in most cases means display: block. So the first idea is to omit keys in cases when they are obvious. CSS does not support «boolean» or «flag» values. This is a place for a mixins, like .block.

2: We often use properties in a composition. Like when you need some special left value, you often need also a top. Or when you specify width you may want to specify height as well in some cases. Sometimes you need block with line of text inside, so you specify both height and line-height of the same value. Mixins, which provide adequate abstractions, like .pos(@top; @left) or .wh(@width; @height) (with a little help of reasonable defaults) may be handy.

3: Using axiomatic mixins allow to write short, well-composed and even poetic definitions for elements. It is a good ground for more high-level mixins.

install & usage

install:

$ npm i @streetstrider/axiom

usage:

/* import whole package */
@import (reference) 'node_modules/@streetstrider/axiom/axiom/index';

/* or pick axioms */
@import (reference) 'node_modules/@streetstrider/axiom/axiom/display';
@import (reference) 'node_modules/@streetstrider/axiom/axiom/flex';

.component
{
	.flex;

	& > .main
	{
		.grow;
	}
}

/* import with namespace */
#axiom
{
	@import (reference) 'node_modules/@streetstrider/axiom/axiom/flex';
}

.component
{
	#axiom > .flex;
	/* or */
	#axiom.flex;

	& > .main
	{
		#axiom > .grow;
	}
	/* or */
	& > .main
	{
		#axiom.grow;
	}
}

license

ISC, © Strider, 2018.