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

kimjansheden-logo

v1.1.1

Published

A React component for displaying Kim Jansheden's branded logo

Readme

Kim Jansheden Logo

Installation

npm install kimjansheden-logo

Quick start (recommended)

Import the package CSS where you use the component. This ships the minimal styles the logo needs (tooltip, transitions, shadows, base sizing) and works with or without Tailwind scanning node_modules.

// Near where you use the component
import 'kimjansheden-logo/styles.css';

Then use the component as usual:

import KimJanshedenLogo from 'kimjansheden-logo';

export function FooterBadge() {
  return <KimJanshedenLogo />;
}

You can still pass Tailwind utilities via className to control size and positioning if Tailwind is present in your project.

Requirements

This component uses Tailwind-style utility classes in its markup. If your project runs Tailwind CSS, the import above often suffices. For Tailwind v4 projects that do not scan node_modules, see the options below.

Tailwind source configuration (v4+)

If you prefer to rely solely on Tailwind-generated utilities (and skip the styles.css import), Tailwind CSS v4 ignores node_modules by default. Register the package explicitly in the stylesheet where you import Tailwind so that utilities used by the component are generated:

/* Register Tailwind at the top of your CSS file */
@import "tailwindcss";
/* Scan the published bundle for utility classes (adjust the relative path) */
@source "../node_modules/kimjansheden-logo/dist";

If you only need a handful of utilities, you can safelist them inline instead of scanning the whole package:

/* Register Tailwind */
@import "tailwindcss";
/* Safelist the tooltip helpers so they are always available */
@source inline("{bottom-full,top-full,mb-2,mt-2,left-0,right-0,left-1/2,-translate-x-1/2}");

Remember to restart your dev server after changing the stylesheet so Tailwind recompiles with the updated sources.

Tailwind 3.x projects

If you are still on Tailwind 3, add the package path to the content array (or safelist the individual utilities) in tailwind.config.{js,ts} instead. The component ships the same classes, so no other changes are required.

VS Code "Unknown at rule @source"

If the stock CSS language service in VS Code does not yet recognize Tailwind's @source directive, you might see a lint warning. Until the Tailwind CSS extension ships full v4 support, you can teach VS Code about the directive by adding custom CSS data in your application:

// .vscode/tailwindcss-v4.custom-data.json
{
  "atDirectives": [
    {
      "name": "@source",
      "description": "Tailwind CSS v4 source registration directive"
    }
  ]
}

Then reference the file from your workspace settings:

// .vscode/settings.json
{
  "css.customData": [".vscode/tailwindcss-v4.custom-data.json"]
}

Restart VS Code afterwards and the warning disappears. Alternatively, install the Tailwind CSS IntelliSense extension preview build once it becomes available, which will include native support for the new directives.

Usage

Import the component

import KimJanshedenLogo from "kimjansheden-logo";
// Recommended: import base styles once near usage
import 'kimjansheden-logo/styles.css';

Use the component

// Use without className – uses default sizes and positioning
<KimJanshedenLogo />

// Use with custom size (uses relative positioning)
<KimJanshedenLogo className="h-6 w-6" />

// Use with custom positioning (uses default size)
<KimJanshedenLogo className="fixed bottom-0" />

// Use with responsive size
<KimJanshedenLogo className="h-4 w-4 md:h-8 md:w-8" />

// Use with fixed position to bottom right
<KimJanshedenLogo className="fixed bottom-4 right-4 h-12 w-12" />

// Use with absolute position to top left
<KimJanshedenLogo className="absolute top-0 left-0 h-8 w-8" />

// Use with relative positioning and offset
<KimJanshedenLogo className="relative top-2 left-4 h-10 w-10" />

Notes

  • Importing kimjansheden-logo/styles.css ensures tooltip and animation styles are present even if Tailwind v4 does not scan node_modules.
  • If you prefer not to import the CSS, configure Tailwind v4 to scan the package using @source as shown above, or safelist the few utilities the component needs.