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

@octo-produits-internes/design-system-components

v0.2.91

Published

Package for implementation of OCTO's design system components

Downloads

14

Readme

OCTO Design System Components

pipeline status

Package for implementation of OCTO's design system components. It includes the standalone @octo-produits-internes/design-system package. A demo storybook is also available.

1. Getting started

Requirements

| Package | Version | | -------------------------------------------------------------------- | -------------------------------- | | react | 16.0.0, 17.0.0, 18.0.0 or higher | | styled-components | 4.0.0, 5.0.0 or higher |

With a package manager

  1. Install the react and styled-components packages (unless you already have them) :
yarn add react styled-components
  1. Install the package :
yarn add @octo-produits-internes/design-system-components
  1. Import the design system package components in your main script :
import { /* see documentation*/ } from '@octo-produits-internes/design-system-components'

On a static website

  1. Add the unpkg.com origin to your script-src and font-src CSPs.

  2. Add the react and styled-components script tags to your HTML page (unless you already have them) :

<script src="https://unpkg.com/react@18/umd/react.production.min.js"></script>
<script src="https://unpkg.com/styled-components@4/dist/styled-components.js"></script>
  1. Add the package script tag to your HTML page :
<script src="https://unpkg.com/@octo-produits-internes/design-system-components"></script>
  1. Import the package namespace in your script :
const { /* see documentation*/ } = OctoDesignSystemComponents

2. Documentation

WIP

3. Development

Clone this repository and install all dependencies with yarn install --check-files. Then, the following commands will be usable :

  • yarn start:example: starts a headless server at localhost:8080 to show a use case example (defined in src/main.example.ts)
  • yarn start:example:ssl: same as yarn start:example but the server will serve over HTTPS, as long as you have both certs/octopod-auth.pem and certs/octopod-auth-key.pem
  • yarn reinstall: reinstalls all dependencies in a clean state
  • yarn build: transpiles the project from Typescript to a Javascript module in dist
  • yarn build:pack: same as yarn build but compiles the code and packs it for browser use
  • yarn build:pack:example: same as yarn build:pack but writes the output pack file to example, alongside all the assets and the source map file
  • yarn build:pack:production: same as yarn build:pack but writes the output pack file to dist/packs, alongside the imported assets and without the source map file
  • yarn test: starts tests for the specified file if specified, all files if not
  • yarn test:watch: same as yarn test, but will run in watch mode
  • yarn test:output: same as yarn test, but will output the results in src/config/jest/jest.result.json
  • yarn test:coverage: same as yarn test:output, but will output the coverage in the console and in src/config/jest/coverage/
  • yarn test:coverage:inspect: same as yarn test:coverage, but will start a headless server at localhost:8081 to show coverage results
  • yarn lint:code: lint the specified TS or TSX file
  • yarn lint:code:all: same as yarn lint:code, but lints on all TS and TSX files
  • yarn lint:style: lint the specified style file
  • yarn lint:style:all: same as yarn lint:style, but lints on all style files

4. License

All rights reserved to OCTO Technology (France). Credit goes to the Produits Internes team. Use for other businesses is strictly prohibited.