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

toasts-react

v0.0.5

Published

Lightweight React toast notification library

Downloads

543

Readme

🚀 React Toast Library

A lightweight, dependency-free React toast notification library with built-in CSS-in-JS style injection, optimized for modern React apps.


📦 Peer Dependencies

This library does not bundle React. You must install the following peer dependencies:

npm install react react-dom

Required versions:

"peerDependencies": {
  "react": "^19.2.3",
  "react-dom": "^19.2.3"
}

✅ This ensures compatibility across multiple React projects without version conflicts.


⚡ Quick Start

1️⃣ Install the library

npm install toasts-react

or

yarn add toasts-react

2️⃣ Inject the Toast Provider (One Time)

Wrap your root application with ToastProvider.

import React from "react";
import ReactDOM from "react-dom/client";
import { ToastProvider } from "toasts-react";
import App from "./App";

ReactDOM.createRoot(document.getElementById("root")).render(
  <ToastProvider>
    <App />
  </ToastProvider>
);

⚠️ Important: ToastProvider must be added once, preferably at the app root.


3️⃣ Show a Toast Anywhere

import React from "react";

import { ToastProvider, useToast } from "toasts-react";

const Button = () => {
  const { success, error, info, warning } = useToast();

  const buttonClick = () => {
    success("Profile updated successfully");
    error("Something went wrong");
    info("New update available");
    warning("Password is weak");
  }

  return <button onClick={() => buttonClick()}>Toast</button>;
}

export default function App() {
  return (
    <ToastProvider>
      <Button />
    </ToastProvider>
  );
}

🎨 How Style Injection Works (CSS-in-JS)

This library uses runtime CSS injection instead of external .css files.

🔹 Why CSS-in-JS?

  • No global CSS conflicts
  • Zero setup required
  • Works in SSR & Micro-frontend apps
  • Fully tree-shakable

🔹 How it works internally

On first render of ToastProvider:

  1. A <style> tag is created
  2. Toast styles are injected into document.head
  3. Styles are injected only once
  4. No re-injection on re-renders
if (!document.getElementById("__toast_styles__")) {
  const style = document.createElement("style");
  style.id = "__toast_styles__";
  style.innerHTML = TOAST_CSS;
  document.head.appendChild(style);
}

✅ Safe for multiple React roots ✅ Safe for Module Federation ✅ Safe for Next.js / Vite / CRA

🏗 Architecture (Deep Dive)

🔹 Core Store

  • In-memory array
  • No external state manager
  • Minimal re-renders

🔹 Rendering Strategy

  • Single ToastContainer
  • Uses React Portals
  • Isolated DOM layer

🧠 Best Practices

✅ Do

  • Mount ToastProvider once
  • Use semantic toast types (success, error)
  • Use IDs for long-running tasks

📦 Bundle Size

  • < 4KB gzipped
  • Tree-shakable
  • No CSS files
  • No icons bundled

🧭 Roadmap

  • ⏳ Swipe-to-dismiss
  • ⏳ Promise-based toast
  • ⏳ Theme tokens
  • ⏳ Accessibility roles

🧑‍💻 Contribution Guidelines

git clone <repo>
npm install
npm run build