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

@bothrs/zeplin

v0.1.5

Published

This script will fetch a styleguide form a Zeplin project, convert it into a variable css file or a tailwind file that can be imported in the tailwind.config

Downloads

55

Readme

Zeplin

This script will fetch a styleguide form a Zeplin project, convert it into a variable css file or a tailwind file that can be imported in the tailwind.config

Getting started

yarn add --dev @bothrs/zeplin

API

The command take a few input flags:

  • --token the bearer token from the Zeplin designer. Can be found under the Zeplin settings
  • --projectId the projectId of the Zeplin project
  • --destination This is is the path to the file where you want your files to be generated. (Example: ./src/styles/variables.css)
  • --tailwind This flag will change some configuration in the theme to make it work with tailwind (optional)

Tailwind config

When you want to use the tailwind feature of the package, you'll need to update the tailwind.config file to use thie design token file. What you need to do is extend your tailwind theme with the file created by the bothrs/zeplin package e.g

const tailwindExtend = require("./tailwindExtend.json");

module.exports = {
  content: [
    "./pages/**/*.{js,ts,jsx,tsx}",
    "./components/**/*.{js,ts,jsx,tsx}",
  ],
  theme: {
    extend: {
      ...tailwindExtend,
    },
  },
  plugins: [],
};

Usage tailwind classes

After you extended the tailwind config with your design tokens you can use the generated custom tailwind classes in your html like this:

<h2 className="text-h1-mb font-h1-mb">Post</h2>

Example command

yarn sync-zeplin --token gh123hf1 --projectId 61c2fc3cbc2bbe6 --destination ./src/styles/variables.css