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

@mxenabled/design-tokens

v1.0.3

Published

Design Tokens

Downloads

7,783

Readme

MX Design Tokens

A simple utility for sharing themed styling information.

Installation

To install the package via npm into another JS project, run the following command:

npm install @mxenabled/design-tokens

To import the default themed objects:

import { light, dark } from '@mxenabled/design-tokens'

To build a custom colored themed object:

import { buildTheme } from '@mxenabled/design-tokens'

const myCustomOverrides = {
  "Color": {
    "Brand300": "green"
  },
  "Custom": {
    "ButtonHeight": 42,
    "InputText": "lime"
  }
}

const greenTheme = buildTheme('light', 'react', myCustomOverrides)

Development Environment

Run the following commands in order to setup a local build environment:

git clone https://github.com/mxenabled/mx-design-tokens.git
cd ./mx-design-tokens
npm i
npm run build:all

Tokens

| Token Output Types | Description | | :---------------------------------------------------------------------------------------- | :----- | | Markdown | documentation for light theme tokens | |   | documentation for dark theme tokens theme tokens | | JSON - React Web Apps | | SCSS - Sass / Rails Apps | | CSS - Other Web Apps | | JSON - React Native Apps (work in progress...) | | JSON - Mobile OS Apps (work in progress...) |

Generate files from Tokens

| Command | Description | | :------------------- | :------------------------------------------------------------------------------------------------------- | | | | | npm run build:all | Builds everything in one easy step | | | | | npm run build | Compile src files out to the dist folder | | npm run build:docs | Compile markdown documentation for viewing all the tokens | | npm run build:json | Compile static JSON files to use as style objects in React Web Apps | | npm run build:scss | Compile static SCSS variables to use in Sass / Rails Apps | | npm run build:css | Compile static CSS variables for use in any web project |

Publishing to NPM

In order to make sure your changes make it to NPM you need to do the following steps in order after adding/changing tokens in the src directory:

  1. Update the package version in package.json
  2. Run npm install so that the package-lock.json updates with the new version
  3. Run npm run build:all to ensure all output files are up to date
  4. Update the CHANGELOG.md with your changes
  5. Merge the code into master
  6. Checkout the master branch
  7. Run npm publish
  8. Enter your OTP(one time password). This is the code from your 2 factor authentication for npm.