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

lll-design

v0.1.1

Published

This the design portion of the @lll/core ecosystem. See https://github.com/Lululemon/lll-core for more details.

Downloads

3

Readme

@lll/design

This is part of the @lll/core. See https://github.com/Lululemon/lll-core for more details.

Overview

A way for design team to stay in sync with base/univerisal styles. This contains a design.sketch with mininal pages that contain univerisal styles like colors, typographies, and more.

Design Team Prerequisites: The Github GUI plugin for Sketch.

This does not require any programing skills just an understand of how to save versions and branch corrrectly via the Github GUI.

Inside @lll/design/

Files | Details | :---:| --- .github | Containes Github Actions src | Files not shared when published to npm. package | Files shared when published to npm.

Inside @lll/design/src

Files | Details | :---:| --- design.sketch | Sketch file contain the following pages:colors (The file structure convention is important for the src/index.js) src/index.js | Reads the design.sketch and converts it to json. Uses helper function then writes parsed out .json files to disk, thus updating the @lll/design package. src/helpers/*.js | Helper functions. The helper name (i.e. src/helpers/[name].js) should match desired outputed .json file name (i.e @lll/design/[name].json)

The design.sketch is only for the design team to stay in sync with eachother. This does not require any programing skills as there is a Github GUI plugin for sketch to publish updates to.

An example of the use case of src/helpers/[name].js files are as follows: Assume the following src/helpers/color.js. This would be a helper function to parse out the colors from provided from src/index.js and publishes a file at src/design/colors.json that the @lll/styleswould use.

package/

output deployed to npm.

Files | Details | :---:| --- package/ |
colors.json | Styles that @lll/styleswould use.

Resources:

Also see ROADMAP.md Also see CONTRIBUTING.md