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

shoelace-react

v1.5.0

Published

React wrappers around the shoelace web components.

Downloads

30

Readme

shoelace-react

React wrappers around the shoelace web components.

But wait, doesn't shoelace already ship with "first class" React support?

Yes. Except it doesn't work for server-side rendering. These wrappers do.

Installation

Add the package as a dependency to your project as normal:

npm install shoelace-react

You must also add Shoelace's theme and module just as if you were using Shoelace directly. Something like this:

<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@shoelace-style/[email protected]/cdn/themes/light.css" />
<script type="module" src="https://cdn.jsdelivr.net/npm/@shoelace-style/[email protected]/cdn/shoelace.js"></script>

You can also follow their docs for cherry-picking or bundling to reduce the download required.

Usage

Import the component you want and use it as a normal react element. The components should have the same props as the official Shoelace react elements so follow their API docs. If there are differences in behaviour then please file an issue.

import { SlAvatar } from 'shoelace-react';

const App = () => (
  <SlAvatar label="User avatar" />
);

You can also import components individually which may allow for a smaller bundle, though this package is fairly small anyway.

import SlButton from 'shoelace-react/components/button';

const App = () => (
  <SlButton variant="default">Default</SlButton>
);

Direct element access

All components also accept a ref prop which gives you access to the custom element. the element class is also exported as a pure type so you can safely import without breaking SSR. Note that as the element is exported as a type you can't use it to construct the element yourself.

import { useRef, useEffect } from 'react';
import { SlButton, SlButtonElement } from 'shoelace-react';

const App = () => {
  let buttonRef = useRef<SlButtonElement>();

  useEffect(() => {
    buttonRef.current.focus();
  }, []);

  return <SlButton ref={buttonRef} variant="default">Default</SlButton>
};

Events

Custom event types are exported for each component:

import { useCallback } from 'react';
import { SlInput, SlInputElement, SlInputChangeEvent } from 'shoelace-react';

const App = () => {
  let changed = useCallback((event: SlInputChangeEvent) => {
    window.alert(event.target.value);
  }, []);

  return <SlInput label="Enter text" onSlChange={changed} />
};

There are a couple of different types you can use in TypeScript for the event:

  • Most specific (SlInputChangeEvent). Here event.target and event.currentTarget are correctly typed to the component type (SlInputElement here). If the event includes any custom detail then that is also correctly typed.
  • Shared across components (SlChangeEvent), event.target is HTMLElement however you can make this more specific by giving the element type as a generic (SlChangeEvent<SlInputElement>).
  • Generic CustomEvent.

If you want to register for the capturing phase of the event just append Capture to the event prop.