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

wmn-design-system

v2.4.0

Published

A library of typography, visual styles and user interface components which are documented for Transport for West Midlands.

Downloads

9,107

Readme

1. TfWM Design System

Netlify Status David Last commit Open Github issues

1.1. Table of contents

1.2. Overview

Welcome to the Transport for West Midlands Design System.

The TfWM design system is ran at the designated url on startup (usually http://localhost:3000) and is the primary means of viewing your work - it will live update as you make changes.

  • Tailored for building Transport for West Midlands apps and websites: Using the TfWM Design System markup and CSS framework results in UIs that reflect the Transport for West Midlands look and feel.
  • Continuously updated: As long as you're using the latest version of the TfWM Design System, your pages are always up to date with Transport for West Midlands UI changes.

1.3. Quick start

You'll need Git and Node.js installed to get this project running.

  1. Clone the project with git clone https://github.com/wmcadigital/wmn-design-system.git
  2. Run npm install in the root folder.
  3. Run npm start to launch the dev environment with hot reloading.
  4. Visit http://localhost:3000

Having trouble getting these steps to work on your machine? Follow the troubleshooting guide.

1.4. Tasks

For more in-depth information on what each task does, see tasks guide.

1.4.1. Starting web server

Start the TfWM Design System web server.

npm start

1.4.2. Linting

Lint the code base for syntax and stylistic errors.

See Linting for more details.

# Lint indentation, Sass, JavaScript files, html
npm run lint:all

# Lint languages independently
npm run lint:styles
npm run lint:templates
npm run lint:scripts

1.4.3. Compilation

Build the design system for various environments

See Building for more details.

# Build Sass, JavaScript, HTML files
npm run build:all

# Build languages/assets independently
npm run build:styles
npm run build:templates
npm run build:scripts
npm run build:images
npm run build:sprites
npm run build:config

1.4.4. Clean up

Delete all built languages/assets including temporary build and local files.

npm run clean

1.5. Troubleshooting

See the troubleshooting guide.

1.6. Contributing to the code base

See the contributing guide.

1.7. Got feedback?

Please open a new Github Issue.