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

coc-common-ui

v0.1.2

Published

- make sure Yeoman is installed globally on your computer - create a folder for your project `cd` into the folder (the root of your new library) - alternately - can be run from root of existing project (will not overwrite your package.json, readme, npmi

Downloads

4

Readme

Coc-common-ui Component Library

Document How to run it

  • make sure Yeoman is installed globally on your computer
  • create a folder for your project cd into the folder (the root of your new library)
  • alternately - can be run from root of existing project (will not overwrite your package.json, readme, npmignore, or gitignore if they already exist)
  • run yo react-library-component
  • Enter component name with spaces. Will automatically TitleCase these to match react best practices and pipe them for wrapper class generation. (We use all lower case, piped, file names and classes)
  • Respond y to prompt about overwriting the coc-common-ui/index.js file. This will not actually overwrite but will append your added component to the end of this file.
  • Alternatly can run yo react-library-component "component name" [function or class] (quotes required when component has a space in it's name)
  • After first time generator runs execute yarn install to download required node modules

Creating Library Components

  • After running the generator you can modify, add, or remove parts of the generated content from your coc-common-ui/[component-name] folder
    • styling done in coc-common-ui/[component-name]/style.scss
    • structure and logic done in coc-common-ui/[component-name]index.js

Document How to build it for production/reuse

  • run yarn create to run babel to compile js code to output directory
  • run npm publish to publish library to npm, .npmignore file has been created for you to include only your compiled library folder.

Document how to use the library in another project

  1. Add the library as dev dependency yarn add coc-common-ui --dev
  2. Example - use library title component:
  • import the component: import {Title} from 'coc-common-ui'
  • use the imported component: <Title text="Testing Library Title Component" />
  1. Make sure Webpack is configured to handle SCSS files

Deleting components from the library

  1. Delete the component's entire folder
  2. Delete the line for the component from the coc-common-ui/index.js file