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

wcg.ui.kit

v0.0.24

Published

[![pipeline status](https://git.ey-intuitive.com/ashtonharris/stencil-demo-with-playbook/badges/develop/pipeline.svg)](https://git.ey-intuitive.com/ashtonharris/stencil-demo-with-playbook/commits/develop) [![coverage report](https://git.ey-intuitive.com/a

Downloads

4

Readme

WCG UI Kit

pipeline status coverage report

Stencil Library with angular and react outputs documented in the playbook. This is an example architecture of how this can work.

Table of Contents

Requirements

  • node >= v10.16.3

Getting Started

Setup the project:

$ yarn setup && yarn build

Start all everything

$ yarn start

Available Scripts

| Command | Description | | ---------------------------- | --------------------------------------------------------------------| | yarn build | Build everything | | yarn build:angular | Build the angular example application | | yarn build:playbook | Build the playbook documentation static site | | yarn build:react | Build the react example application | | yarn build:stencil:angular | Build the angular wrapper library of the stencil component library | | yarn build:stencil:react | Build the react wrapper library of the stencil component library | | yarn build:stencil | Build the stencil library | | yarn clean | Remove all node modules, lock files, and compiled/ignored code | | yarn lint:angular | Lint the angular example application | | yarn lint:js | Lint all .js files | | yarn lint:scss | Lint all .scss files | | yarn lint:stencil | Lint the stencil library | | yarn lint | Lint everything | | yarn serve:playbook | Start the playbook server | | yarn setup | Install, link, and build all necessary packages to get started | | yarn start | Start and watch everything | | yarn start:angular | Start and watch the angular example application | | yarn start:react | Start and watch the react example application | | yarn start:stencil | Start and watch the stencil library | | yarn test | Test the stencil library | | yarn test:watch | Test the stencil library in watch mode |

Generate Library Items

In order to generate a new stencil component:

$ wcg --cmd generate --type component --name <component-name>

To generate an example for a component:

$ wcg --cmd generate --type example --name <component-name> --exampleName <example-name> --playbookDir <playbook-group-name>

After Generating a new component or an example remember to run a new build:

$ yarn build

Environments

| Environment | Url | Branch | | ------------|---------------------------------------------------------|---------| | DEV | TBD | develop | | QA | TBD | qa | | PROD | TBD | master |

Publishing

Update package versions

To change the version number in all package.json files, in the root directory, run the following command, replacing <update_type> with one of the semantic versioning release types (patch, major, or minor)

$ node bin/release <update_type>

Build all libraries and docs:

$ yarn build

Publish all packages:

$ node bin/publish

Commit and push the changes:

git add .
git commit -m "Release <version>"
git push