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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@kite-tech/components

v7.0.5

Published

Shared components to be used throughout Kite front end apps.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

kite-machine-userkite-machine-userdbothadbothatomgallardtomgallardsylwester.smolensylwester.smolenmattkaymattkaya7xsva7xsv

Keywords

Readme

Kite Components

Shared Angular components, SCSS styles and SVGs to be used throughout Kite front end apps.

The app contains an example page where examples of the components can be seen.

Tables of contents

Examples

To view examples of the various versions of the app go to:

Requirements

  • Node v8+
  • Npm 5+
  • Gulp v3

Development

  • Clone the app

  • npm i install dependencies

  • npm start run development server and watch for file changes

  • npm run build:dist build dist versions of the app for each partner

  • npm t runs tests

  • npm run test:watch runs tests and watches for changes

  • npm run test:dist runs tests and produces code coverage

Usage

Components

  • npm i @kite-tech/components --save: install via NPM
import {
    FocusOnInitModule,
    ModalModule,
    SvgHrefModule,
} from '@kite-tech/components';

Styles

  • npm i @kite-tech/components --save: install via NPM

Include via SCSS

@import './node_modules/@kite-tech/components/styles/components/components.text';
@import './node_modules/@kite-tech/components/styles/components/components.title';
@import './node_modules/@kite-tech/components/styles/components/components.icons';
@import './node_modules/@kite-tech/components/styles/components/components.button';
@import './node_modules/@kite-tech/components/styles/components/components.modal';
@import './node_modules/@kite-tech/components/styles/components/components.loading-spinner';

Commit linting

We use the config-conventional setup to lint the commits. See details of this here:

Publishing

When running npm publish, the prepublishOnly script will run. If the version contains text e.g 2.0.1-alpha.1, nothing will happen. However if the version doesn't have any tags, e.g 2.0.1 then the script will do the following:

  • Go to the gh-pages branch
  • Merge in the changes from the current branch
  • Build a dist version of the components in the folder /docs/{{version-number}}
  • Create a README.md file in the docs/{{version-number}} folder detailing the changelog and the previous version
  • Update the index.html of the docs directory with links to the new version
  • Push the changes to the gh-pages branch and switch back to the original branch.