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

letrus-ui

v2.68.0

Published

## Getting started

Downloads

649

Readme

Letrus Components Lib

Getting started

Clone the repository with:

git clone [email protected]:letrustech/letrus-ui.git

Move to the root folder and install all the dependencies using yarn:

To run the project you must create a .env file in the root folder and paste the variables regarding your operational system from .env-example file

yarn

The design system lib is organized using Storybook. To run the project execute:

yarn start

and open the browser in: http://localhost:9009/

During development, following the TDD approach, we write tests before. To run Jest in whatch mode use:

yarn test

The folder/files tree of a Component is located into src/components/ and is composed by:

├── src
│   ├── components
│   │   ├── [ComponentName]
│   │   │   ├── [ComponentName].module.scss
│   │   │   ├── [ComponentName].stories.tsx
│   │   │   ├── [ComponentName].test.tsx
│   │   │   └── index.tsx

The index.tsx is the main component file, usually a Functional Component like:

import React from 'react';
import styles from './Title.module.scss';

export interface TitleProps {
  title: string;
}

const Title: React.FC<TitleProps> = props => (
  <h1 className={styles.title}>{props.title}</h1>
);

export default Title;

For the style, we use SCSS Modules that allow to import the class styles into the component and use them as objects (i.e. className={styles.title}). The .scss file is a common SCSS file, with all the functionalities of SCSS. Style utils should be stored in src/styles folder and the specific util file should be named with an _ at the beginning of the file name, since its scope is as a private file. Inside the SCSS Modules files for each component, should be added the typography file and colors imports to apply the default Typography and Colors to all components created.

@import 'styles/letrusTheme';

.title {
  background-color: $primary;
}

The [ComponentName].test.tsx is the testing file, that uses Jest and React Testing Library. A basic structure is like:

import React from 'react';
import {render} from '@testing-library/react';
import Title from './index';

it('renders a welcome message', () => {
  const {getByText} = render(<Title title="Doh!" />);
  expect(getByText('Doh!'));
});

The [ComponentName].stories.tsx is the Storybook file. An example story is:

import React from 'react';
import Title from './index';

export default {
  title: 'Design System/Title',
  component: Title,
  parameters: {
    info: {
      text: 'Foo component'
    }
  }
};

export const Default = () => <Title text="Foo" icon="thumbs-up" />;

To automatically create a new Component, install the VSCode extension Blueprint and then, right click in src/components folder and select the item New File from Template. In the opened menu, select ui-component and then write the component name in the input field.