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

@core-ds/primitives

v2.5.2

Published

<img width="100%" alt="primitives2" src="https://user-images.githubusercontent.com/705973/52524183-56715680-2c68-11e9-8156-a1e81baa6201.png">

Downloads

214

Readme

npm version

Installation

npm install @core-ds/primitives

Usage

JavaScript

After installing the @core-ds/primitives npm package, you can import and apply it in any JavaScript/TypeScript file:

import styled from "styled-components";
import { color, space } from "@core-ds/primitives";

const Example = styled.div`
  color: ${color.white};
  background-color: ${color.blue[500]};
  padding: ${space[4]};

  &:hover {
    background-color: ${color.blue[800]};
  }
`;

LESS

LESS Core Primitives are globally available in every LESS file in the iFixit/ifixit repo:

element {
  color: @color-white;
  background-color: @color-blue-500;
  padding: @space-4;

  &:hover {
    background-color: @color-blue-800;
  }
}

See the complete list of LESS variables here.

CSS Custom Properties (Variables)

CSS Core Primitives are globally available on the :root (html) element. They can be used in any (P)HTML file:

/* excerpt from core-primitives.css */
:root {
  --color-black: #11161a;
  --color-white: #fff;
  ...
  --color-blue-500: #3b82f6;
  --color-blue-600: #2563eb;
  --color-blue-700: #1d4ed8;
  --color-blue-800: #1e40af;
  ...
  --space-3: 12px;
  --space-4: 16px;
  --space-5: 24px;
  ...
}
/* style the element */
element {
  color: var(--color-white);
  background-color: var(--color-blue-500);
  padding: var(--space-4);

  &:hover {
    background-color: var(--color-blue-800);
  }
}

See the current list of CSS Custom Properties here.

For more capabilities, check out the MDN Custom Properties article

Contributing

Local development setup

Follow these steps to get the project setup on your local machine:

# Clone repo
git clone https://github.com/iFixit/core-primitives.git && cd core-primitives

# Install dependencies
npm install

Adding or Updating Primitives

1. Create a new branch

Create a new branch for your changes:

git checkout -b <branch>

2. Commit and push changes

Apply your changes to index.json, and keep index.d.ts in sync.

3. Test your build

Run npm run build and verify core-primitives.css and core-primitives.less are correct.

4. Open a pull request

Use GitHub to create a pull request for your branch.

5. Bump the package version

After your pull request has been approved, bump the package version by running:

npm version [major | minor | patch]

Running npm version will build, bump the version, and write the new data to package.json and package-lock.json. It will also create and push a version commit and tag.

Note: In the context of @core-ds/primitives, significant changes to the library or workflow, or removing primitives would be considered a major update, adding or updating primitives would be considered a minor update, and fixing primitives would be considered a patch. Non-code changes (e.g. documentation) do not require a version bump.

6. Publish to NPM

npm publish

7. Create a release

After your pull request has been merged, create a new release to document your changes. Use the tag you generated in step 4 to create the release.

Done 🎉