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

@fleet.co/tarmac

v3.10.47

Published

Tarmac : Fleet.co Design System

Downloads

894

Readme

Tarmac : Fleet Design System

NPM JavaScript Style Guide

List of components

  • Modal ({Modal})
  • Confirmation Modal : yes or no modals ({ConfirmationModal})
  • Alert : alert message, mainly used in modals ({Alert})
  • Switch/Toggle ({Switch})
  • Label ({Label})
  • Line : grey line to separate items ({Line})
  • Title ({Title})

Install

npm install @fleet.co/tarmac

Use local version in your project

First, make a local copy of this repo and reach to its folder with your IDE. Run command

npm build

This will create a dist folder. Reach to it with your IDE and run command

npm link

Now reach to your project's folder and run

npm link @fleet.co/tarmac

In your project's folder, navigate to your node_modules/react folder then

npm link

Go back to the Design System folder and

npm link react

This will create 2 symlinks to use your local DS in your local project. Now launch your design system and your project

npm run start

Use example

To ease the new components creation, you will find an example project within the Design System itself. To launch it, navigate to your DS folder/example and write

npm run start

In the App.js file in the example folder, call your newly created components as described in "Usage" section.

Publish a new version

To publish the new version of your DS to npm, run

npm run publish-package

This will create a new build, patch the current version, publish to npm and push changes to master. If everything went smoothly, you will see the following message in your IDE : "Design System successfully updated to X.X.X"

Wait for the new version to be released on npm, then go back to your project's folder and install it

npm i @fleet.co/tarmac

Usage

import React from 'react'

import { MyComponent } from '@fleet.co/tarmac'

const myPage = () => {
  return <MyComponent />
}

Troubleshooting

In case you're facing issue at installing the DS locally, please make sure no process is currently running in both your project and the DS. If so, kill them all and try the "use locally" procedure again. You may also have to delete your node_modules folders in both your project and the DS. Then reinstall all packages in both folders and try the "use locally" procedure again. If you get an error related to React Hooks after launching your project, it is probably related to the fact you have two different instance of React running in your project and in the DS (ie your symlink didn't work). Kill all process, redo the react symlink and start again.

License

MIT © @fleet.co