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

ctia-ui

v0.25.0

Published

Bootstrapping a UI component library for CTIA projects

Downloads

426

Readme

CTIA UI Library

Let's make things easy (and beautiful :sparkling_heart:)

Supported components

  • [x] Bubble
  • [x] Buttons:
    • [x] ActionButton
    • [x] DeleteButton
    • [x] DownloadButton
    • [x] LoaderButton
  • [x] Checklist
  • [x] Divider
  • [x] Icons:
    • [x] IconAwesome
    • [x] IconBase
    • [x] IconLabel
  • [x] InfoBar (WellInfo previously)
  • [x] InlineDatepicker
  • [x] InlinePreloader
  • [x] Labels:
    • [x] ContinueLabel
  • [x] NoData
  • [x] Pager
  • [x] PagerPageSize
  • [x] PagerStatusFilter
  • [x] Preloader
  • [x] Switcher
  • [x] Tooltip:
    • [x] TooltipBase
    • [x] TooltipIcon
  • [x] UploadInstructions
  • [x] WithModal

Run local version of library

Install dependencies with yarn install or npm install.

Run yarn dev or npm run dev to start local dev server (will be run on http://localhost:1234).

To test locally import your components inside src/docs/index.js then use components inside render method. This file already will have recently added examples.

Build new version

yarn build then yarn build:docs

Integration with other projects

To add the UI library for a first time:

npm i ctia-ui or yarn add ctia-ui

To upgrade the current version:

npm update ctia-ui or yarn upgrade ctia-ui

Upgrade UI Library version

When time to update library comes (new components added or improved), follow next steps to update the library version.

  • Be sure that your code is well tested, then commit it
  • Increase verion number inside package.json and commit this change
  • Build new version and commit results (TODO: add gitlab worker to build new version)
  • Update related projects (yarn upgrade ctia-ui or npm update ctia-ui)

Shell script draft (building automation process)

Example:

build.sh -v patch -m "Commit message"

Input params:

  • commit message (string)
  • release type (oneOf: ['patch','major','minor'])

Patch example: 1.0.1 -> 1.0.2 (Increment the third digit) Minor example: 1.0.12 -> 1.1.0 (Increment the middle digit and reset last digit to zero) Major example: 1.3.54 -> 2.0.0 (Increment the first digit and reset middle and last digits to zero)

Details: https://docs.npmjs.com/about-semantic-versioning

Script flow:

  • run build and then build:docs command
  • commit and push changes to git (need to ask comment message as a param)
  • change package version (npm version <update_type>, see release type input param)
  • publish changes to npm (npm publish)