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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@kepler-io/core-react

v1.0.47

Published

This project represents the Kepler React library.

Readme

Kepler Lib - React

This project represents the Kepler React library.

Build

Run yarn build.

Installation

Kepler Node Lib is installable as NMP Module: npm install @kepler-io/core-react.

Upgrade of package is available via command: npm upgrade @kepler-io/core-react

Packing

You can test packaging locally via npm pack and observe generated tar file.

Publishing

Publishing is done via NPM (not Yarn): npm run publish-remote.

https://www.npmjs.com/search?q=kepler-io

Versioning

In order for your publish to be successfull you must increment the version on the package.json file following the instructions below:

Given a version number MAJOR.MINOR.PATCH, increment the:

  • MAJOR version when you make incompatible API changes,
  • MINOR version when you add functionality in a backwards compatible manner, and
  • PATCH version when you make backwards compatible bug fixes.

You can test your local features using a pre-release version, following the rules below:

  • A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version.
  • Identifiers MUST comprise only ASCII alphanumerics and hyphens [0-9A-Za-z-].
  • Identifiers MUST NOT be empty. Numeric identifiers MUST NOT include leading zeroes.
  • Pre-release versions have a lower precedence than the associated normal version.
  • A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version.

Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92, 1.0.0-x-y-z.–.

Styling

To contribute to styling, there are a couple of rules to follow:

  • We use stylelint to enforce style rules. Please install IDE extension to make sure you get instant linter feedback
  • Go through all defined variables in files in styles folder, and use them in your code.
  • We strive to have our design as flexible as possible, therefore we design in pixels, and code in rems. To take advantage of this, use prem function available in the _sizes.scss"` file.
  • Our styles are component-based, using CSS Modules. We're enforcing camelCase class names. We don't use BEM.