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

@k-int/stripes-kint-components

v5.6.1

Published

Stripes Component library for K-Int specific applications

Downloads

1,979

Vulnerabilities

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

Links

Git

Maintainers

ianibboianibbokint-adminkint-adminethanfreestonekintethanfreestonekint

Keywords

Readme

stripes-kint-components

A repository to hold components designed to bridge the gap between K-Int's web toolkit based backend modules and stripes.

Installation and usage

Simply run

yarn add @k-int/stripes-kint-components

This repository is available as a public NPM and is pre-transpiled, so it should be ready to work immediately.

In the case where components from this repository require translations, it will need to be added to the stripesDeps array in the implementing module's package.json.

Development

In order to develop this module within a stripes workspace, a couple of steps are needed

  • An environment variable must be set up (See https://chlee.co/how-to-setup-environment-variables-for-windows-mac-and-linux/), STRIPES_TRANSPILE_TOKENS="@k-int"
  • Clone this repository git clone [email protected]:knowledge-integration/folio/stripes-kint-components.git
  • Ensure your branch's kint-components version is at least in line with, or higher than the latest released artifact version (THIS SHOULD NOT BE MERGED TO MAIN: Release versions are controlled by the semantic releases plugin at release time.)
  • Nuke your workspace node_modules and rebuild

What went wrong

  • If you aren't seeing changes take effect double check
    • Your environment variable is definitely set printenv STRIPES_TRANSPILE_TOKENS on Linux, Windows may differ
    • The es directory does not exist inside your local copy of kint-components. When built, this directory is constructed, and will take precedence if present, so if present, always delete for development work
  • If you aren't seeing translations properly, ensure stripes-kint-components is present in the stripesDeps of your implementing module

Documentation

The gitlab repository for this project can be found here.

Quick links

Release Matrix

Please note, the "Flower releases" does not indicate final compatibility. In theory, as a built 3rd party artifact, v1 of kint-components should still actually work with an otherwise Orchid (say) frontend.

However as a developer using kint-components locally, the compatibility will differ.

If the compatibility chart below states compatible with a certain flower release and that is not found, check copies of @folio/stripes, @folio/stripes-core in the workspace with yarn why. It is possible that kint-components 2.8.6, say, is compatible with ^6.0.0 of stripes-erm-components (6.0.0 -> Kiwi), which pulls in 6.2.2 on build (6.2.2 -> Morning Glory) and that that difference causes an issue on build locally which would not be present in any production system, and can be worked around by locking the troublesome dependency to the correct one for the release at hand locally.

Release major | Latest release | Flower releases present in (ERM) | Flower compatibility --- | --- | --- | --- | v1 | 1.7.x | Lotus | Kiwi - Morning Glory | v2 | 2.8.x | Morning Glory | Kiwi - Morning Glory | v3 | 3.2.x | Nolana | Morning Glory - Nolana | v4 | 4.7.x | Orchid | Morning Glory - Orchid | v5 | 5.5.x | Poppy, Quesnalia | Morning Glory - Quesnalia+ |