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

@kokitotsos/react-components

v4.1.0

Published

[![Build Status](https://github.com/kits-ab/react-components/workflows/build/badge.svg?branch=master)](https://github.com/kits-ab/react-components/actions?query=workflow%3Abuild) [![NPM Version](https://badge.fury.io/js/%40kokitotsos%2Freact-components.sv

Downloads

52

Readme

KITS Components

Build Status NPM Version

This component library includes all of the components that are used to build https://kits.se and other React applications that we create and use at KITS.

To install the library, run npm install --save @kokitotsos/react-components

Checkout https://react-components.kits.se for examples and documentation.

Development

You can use any editor for development (Visual Studio Code, Atom, WebStorm, IntelliJ, Vim, ...) but you should make sure that it supports the following technologies:

  • TypeScript – Since the project is written in TypeScript
  • EditorConfig – To help the editor use the correct encoding, indentation, ...
  • Styled Components – To support styled component that we use for styling our components
  • Prettier – To format the code according to our coding conventions

The code is automatically formatted when you commit code. It is also linted before you push the commits to the server.

For debugging purposes you should install React Developer Tools.

Preparations

Available scripts

When you've checked out the code and all dependencies have been fetched you probably want to run npm start but you can run any of the the following scripts:

  • npm run build – Creates a production ready builds in dist/ and dist-styleguide/
  • npm run build:lib – Creates a production ready build of the library in dist/
  • npm run build:styleguide – Creates a production ready build of the styleguide in dist-styleguide/
  • npm run clean – Removes all generated files
  • npm run format – Format the entire codebase using Prettier
  • npm run icons – Generate new icon-components from resources/icons/*.svg
  • npm lint – Lints all code with ESLint and Stylelint
  • npm start – Starts a local styleguide server with hot reloading enabled on http://localhost:6006 to one or more host projects.

Creating a release

All commits to master must go through a pull request and when all relavant pull requests have been merged you can create a release in GitHub and that will automatically trigger a publish to NPM.

Before you do a release, make sure you've updated the version. The easiest way to do this is to use npm version. This will update package.json, create a Git tag and commit all changes. If everything looks as you expect, you can push the changes.

License

Copyright 2022 KITS AB

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this work except in compliance with the License. You may obtain a copy of the License in the LICENSE file, or at:

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.