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

@design-system-rte/react

v1.18.0

Published

React components for Luciole (RTE Design System)

Downloads

569

Vulnerabilities

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

Links

Git

Maintainers

diazailan-rtefrancediazailan-rtefrancejeremyrts-rtefrancejeremyrts-rtefrancethomascandillethomascandille

Keywords

design-systemreactcomponentsuirtestorybookaccessibility

Readme

Installation

npm install @design-system-rte/react

@design-system-rte/core is installed automatically as a dependency. See the root README for other packages.

Setup

  1. Add Design System base styles:

    import "@design-system-rte/react/style.css";

createRoot(document.getElementById("root")!).render(
  <StrictMode>
    <App />
  </StrictMode>,
);

  2. Add Branding/Theme Mixin:

    Include the branding/theme mixin in your main .scss file. This will create a style scope for the components. (If you don't have scss support, you can use the .css files in @design-system/core/css/rte-themes.css and add them to your main styles file).

    @use "@design-system-rte/core/design-tokens/tokens/mixins" as *;

@include theme-selector("bleu_iceberg", "light");

  3. Add HTML Selector:

    Add an HTML selector to define the context for applying component styles.

    <body data-theme="bleu_iceberg" data-mode="light">
  ...
</body>

    data-theme is required on each themed scope. When data-mode is omitted, the mode is inherited from an ancestor carrying data-mode. If no ancestor defines a mode, light is used as the default.

  4. Use Components:

    Implement the different components as documented in the Storybook provided with the library.

Routing / SPA navigation

By default, navigable components (Link, NavItem, NavMenu, SideNav, Header, Breadcrumbs) render a native <a> tag, which triggers a full page reload. To enable client-side (SPA) navigation with the router of your choice you can inject its Link component instead of the native <a> tag. This mechanism has no dependency on any routing library: you provide the component, the design system just renders it.

You can do it using via NavigationProvider configured once at the root of your app.

import { NavigationProvider } from "@design-system-rte/react";
import { Link as RouterLink } from "react-router-dom"; // or any other router library

<NavigationProvider linkComponent={RouterLink}>
  <App />
</NavigationProvider>;

You can also use the customLinkComponent prop on the Link component to override the default behavior for a specific link.

import { Link as RouterLink } from "react-router-dom"; // or any other router library
<Link to="/home" label="Home" customLinkComponent={RouterLink} />;

Without any configuration, all components keep rendering our native <Link> component — this is fully backward compatible.