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

@everchron/ec-shards

v9.17.14

Published

Everchron Shards UI Library

Downloads

2,981

Readme

Everchron Shards

Using Shards

To use ec-shards in your project, install the NPM package and make sure to always use the latest stable version.

yarn add @everchron/ec-shards

Building Shards

This repository contains the design system and Vue components for the Everchron web application.

You will need the following software to setup the development environment. The titles under "Software" in the grid below are linked to the procedures you need to follow.

| Software | Install (macOS) | Install (Linux) | Install (Windows) | |------------------------------------------------------|-------------------------------|-------------------------------|-------------------------------| Node | Follow Site Instructions | Follow Site Instructions | N/A |

Expected node version: >= 20.5.0

Project setup

| Command | Description | | --- | --- | | npm install | Install the dependencies | | npm run dev | Compiles and hot-reloads for app development | | npm run build | Compiles, minifies, and builds package | | npm run test | Run Unit Tests with Vitest | | npm publish --access public | Publishes built package to npm (main branch). Note: You must be logged into npm with an account that has access to the @everchron organization. Additionally, you need to bump the version number in package.json before publishing. | | npm publish --access public --tag beta | Published built package to npm with a feature/branch tag |

Recommended IDE Setup

VSCode + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).

Customize configuration

See Vite Configuration Reference.

Storybook

Storybook provides a sandbox to build UI components in isolation. You can view Storybook hosted on Github pages here.

To view Storybook visit http://localhost:6006/ in your browser.

| Command | Description | | --- | --- | | npm run storybook | Compile stories and run Storybook locally | | npm run build-storybook | Build a static version of Storybook, hosted on Github pages |

Design Tokens

The shards design system runs on design tokens, a system that allows you to define styles once, in a way for any platform or language to consume. A single place to create and edit your styles, and a single command exports these rules to all the places you need them. Tokens are defined in src/tokens/src/tokenfile.json and built into src/tokens/build/platform/file.x.

Command to rebuild all token files: npm run build-tokens

Running Tests

Tests are ran by Vitest. To run tests, use the following command:

npm run test

If you would like to view the testing dashboard, or run tests via the UI, use the following command:

npm run test:ui