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

@pega/cosmos-react-core

v7.0.0-build.17.6

Published

Cosmos is a visual design system and UI component collection. Its goal is to empower application developers in their pursuit to create engaging and rewarding user experiences.

Downloads

4,922

Readme

Welcome to Cosmos!

Cosmos is a visual design system and UI component collection. Its goal is to empower application developers in their pursuit to create engaging and rewarding user experiences.

Getting started

Using Cosmos in your app

The recommended approach for using Cosmos is individual component imports to bundle with a method of your choosing.

import ReactDOM from 'react-dom';
import { SomeComponent } from '@pega/cosmos-react-core';

ReactDOM.render(<SomeComponent {...props} />, el);

Developing Cosmos components

Cosmos adheres to the following code style guides:

  • Javascript: https://github.com/airbnb/javascript
  • CSS: https://github.com/airbnb/css
  • React(Followed loosely at the moment): https://github.com/airbnb/javascript/tree/master/react

These are enforced by ESLint, Prettier and Stylelint with settings some overridden/ignored. If you feel a certain coding style is better suited this project or should be allowed please speak up and advocate. Shoot for consistency and cleanliness.

With that, please take a moment to setup Visual Studio Code. We require the following extensions to be installed:

Cosmos will check the format of your code and fail builds on linting errors so best to have your workspace in sync as you go. Next...

Clone Cosmos:

$ git clone https://github.com/pegasystems/cosmos-react.git

Install node_modules:

$ npm i

Start Cosmos dev server to run Storybook:

$ npm run start:stories

Create your first component - Component names must capitalized, containing only letters:

$ npm run create:component name:YourComponent [type:fn(default)|class|ref] [test:false(default)|true]

This cmd will generate a directory at /packages/cosmos-core/components/YourComponent/ with the following files:

  1. YourComponent.tsx - A React component populated with some basic boilerplate
  2. YourComponent.stories.tsx - A file used for the Storybook documentation that will hold demo components
  3. YourComponent.test.ts - An empty file to use for test code, optional
  4. index.ts - An index file that will re-export the default export from your component file

Inside YourComponent.tsx will be some initial boilerplate:

import { forwardRef, FunctionComponent, PropsWithoutRef, Ref } from 'react';
import styled from 'styled-components';

import { BaseProps, ForwardProps, PropsWithDefaults } from '../../types';
import { defaultThemeProp } from '../../theme';

export interface YourComponentProps extends BaseProps {
  ref?: Ref<HTMLDivElement>;
}

type YourComponentPropsWithDefaults = PropsWithDefaults<YourComponentProps>;

const StyledYourComponent = styled.div<YourComponentPropsWithDefaults>``;

StyledYourComponent.defaultProps = defaultThemeProp;

const YourComponent: FunctionComponent<YourComponentProps & ForwardProps> = forwardRef(
  (props: PropsWithoutRef<YourComponentProps>, ref: Ref<HTMLDivElement>) => {
    return <StyledYourComponent ref={ref} {...props} />;
  }
);

export default YourComponent;

The YourComponent.stories.tsx file will provide a hot reloading dev environment in Storybook:

import YourComponent from './YourComponent';

// These are settings that storybook will use to render your component's stories
export default {
  title: 'Components/YourComponent',
  component: YourComponent
};

// This is the first story in your component's story book section
export const firstYourComponent = () => <YourComponent>Hello YourComponent</YourComponent>;