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

cm-pg-components

v0.2.131

Published

This repository contains all React components needed by Portfolio, Campaign and Licenses and will be released as an npm package.

Downloads

789

Readme

cm-pg-components

This repository contains all React components needed by Portfolio, Campaign and Licenses and will be released as an npm package.

Installation

This project works with:

  • Node/ExpressJs
  • React
  • StoryBook

Node

To install node you can download the latest release or install nvm. NVM is recommended.

NVM

After install nvm, in the root of project run:

nvm install

Getting Started

Install dependencies:

npm  install

Run components documentation:

npm run storybook

The project runs in http://localhost:6006

Local development

To test locally we have two ways:

  • Directly in the app
  • Using Storybook

Directly in the app

Build the package and link it with the app. Make sure that you set as true the LOCAL_DEV variable in the environment variables.

In appsuite-shared directory:

npm run build
npm link

In the app directory

npm link cm-pg-components

Remember after any change the code execute:

npm run build

Using Storybook

Storybook is a components repository, each component that has a stories.jsx file will be listed in that repository.

creating a stories.jsx file

This file imports the component and passes properties to it. The file must be located in the same directory the file component

/Button
-- index.js
-- Button.stories.jsx

Button.stories.jsx

import React from 'react'
import ModalErrors from './'

const defaultsArgs = {
  href: '#',
  className: 'my-class'
}

const ButonToTest = args => (
  <Button { ...args }>
    This is a button
  </Button>
)

export const Default = Template.bind({})
Default.args = {
  ...defaultsArgs
}

export const Secondary = Template.bind({})
Secondary.args = {
  ...defaultsArgs,
  color: 'secondary'
}

export default {
  title: 'Buttons/Button',
  component: Button
}

React components

ReactJs works with reusable components regardless of context. The components work as an independent whole, in that sense each component has its own images, styles, translations, etc. Follow these rules when creating a component:

  • A component can define nested components. You cannot define or use pages.
  • A page can define components, scenes and/or services.
  • Nested features can only be used by their parents.

Components

The components are stored in the components directory. This directory is global and can be used by any part of the applications.

Nested components

A nested component is a component that is defined inside another component; it can only be used by its parent; when a component is needed but it will not be used in more than one place.

Structure

/src
  /components
    /molecules
      /Notifications
        /components
          /ButtonDismiss
            /index.js
        /actions.js
        /index.js
        /reducer.js