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

c10amityui

v2.15.20

Published

c10 Amity UI - Fork

Downloads

24

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

eddie-at-curve10-npmeddie-at-curve10-npmecurve10ecurve10claytonkclaytonk

Keywords

Readme

c10 Amity UI - Fork

Getting started

Installation

  1. git clone https://github.com/curve10-projects/c10-amity-uikit.git
  2. cd ./c10-amity-uikit
  3. ensure you are in prod branch
  4. npm ci or npm ci ---legacy-peer-deps if you get an error
  5. update .env with api key and region, users can be mocked/fake names (i think?)
Develop locally in parallel with a product
  1. install yalc globall if you don't have it npm i yalc -g
  2. build the ui kit: npm run build
  3. yalc publish in c10-amity-uikit directory
  4. yalc add c10amityui in adminsite repo
  5. npm install in FE repo if this is the first time you've added it (use --legacy-peer-deps if error)
  6. Please branch from prod, and work in your own branch.
  7. When you are done, yalc remove --all (from the adminsite folder) (PLEASE ENSURE YOU DON'T COMMIT TO FE WITH THE YALC REFERENCE PRESENT) YALC documentation: https://github.com/wclr/yalc

Develop with Storybook

  1. npm run storybook
  2. http://localhost:6006/ to view sotrybook and update UI
  3. Please branch from prod, and work in your own branch.

Publish changes to NPM

  1. Update the version number in package.json (check npm or prod branch to ensure correct version)
  2. stage and commit all changes.
  3. merge changes into prod branch
  4. open prod brach
  5. npm run build
  6. npm publish (only curve10 team members currently have npm credentials) Once published, rebuild product FE enviroment, and UI kit changes should be pulled in.

Documentation

Please refer to our online documentation at https://docs.amity.co or contact a Ui-Kit representative at [email protected] for support.

Contributing

See our contributing guide