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

@zsviczian/excalidraw

v0.18.0-86

Published

Excalidraw as a React component

Readme

Excalidraw

Excalidraw is exported as a React component that you can embed directly in your app.

Installation

Install the package together with its React peer dependencies.

npm install react react-dom @excalidraw/excalidraw
# or
yarn add react react-dom @excalidraw/excalidraw

Note: If you want to try unreleased changes, use @excalidraw/excalidraw@next.

Quick start

The minimum working setup has two easy-to-miss requirements:

  1. Import the package CSS:
import "@excalidraw/excalidraw/index.css";
  1. Render Excalidraw inside a container with a non-zero height.
import { Excalidraw } from "@excalidraw/excalidraw";
import "@excalidraw/excalidraw/index.css";

export default function App() {
  return (
    <div style={{ height: "100vh" }}>
      <Excalidraw />
    </div>
  );
}

Excalidraw fills 100% of the width and height of its parent. If the parent has no height, the canvas will not be visible.

Next.js / SSR frameworks

Excalidraw should be rendered on the client. In SSR frameworks such as Next.js, use a client component and load it dynamically with SSR disabled.

// app/components/ExcalidrawClient.tsx
"use client";

import { Excalidraw } from "@excalidraw/excalidraw";
import "@excalidraw/excalidraw/index.css";

export default function ExcalidrawClient() {
  return (
    <div style={{ height: "100vh" }}>
      <Excalidraw />
    </div>
  );
}
// app/page.tsx
import dynamic from "next/dynamic";

const ExcalidrawClient = dynamic(
  () => import("./components/ExcalidrawClient"),
  { ssr: false },
);

export default function Page() {
  return <ExcalidrawClient />;
}

See the local examples for complete setups:

LLM / agent tips

If an LLM or coding agent is setting up Excalidraw, these shortcuts usually save more time than re-prompting:

  • Start with a plain <Excalidraw /> in a 100vh container. Add refs, initialData, persistence, or custom UI only after the base embed works.
  • If the canvas is blank, check the CSS import and parent height first. Those are the two most common integration failures.
  • In Next.js or other SSR frameworks, assume client-only rendering first. Use "use client" and dynamic(..., { ssr: false }) before debugging hydration or window is not defined errors.
  • If imports or entrypoints are unclear, inspect node_modules/@excalidraw/excalidraw/package.json. The installed package exports are the source of truth.
  • Do not set window.EXCALIDRAW_ASSET_PATH unless you are intentionally self-hosting fonts/assets.
  • When docs and generated code drift, copy the nearest working example from this repo, especially examples/with-nextjs or examples/with-script-in-browser.

Migrating to @excalidraw/[email protected]

Version 0.18.x removes the old types/-prefixed deep import paths. If you were importing types from @excalidraw/excalidraw/types/..., switch to the new type-only subpaths below.

| Old path | New path | | --- | --- | | @excalidraw/excalidraw/types/data/transform.js | @excalidraw/excalidraw/element/transform | | @excalidraw/excalidraw/types/data/types.js | @excalidraw/excalidraw/data/types | | @excalidraw/excalidraw/types/element/types.js | @excalidraw/excalidraw/element/types | | @excalidraw/excalidraw/types/utility-types.js | @excalidraw/excalidraw/common/utility-types | | @excalidraw/excalidraw/types/types.js | @excalidraw/excalidraw/types |

Drop the .js extension. The new package exports map resolves these paths without it.

These deep subpaths are for import type only. Runtime imports should come from the package root, plus @excalidraw/excalidraw/index.css for styles.

For example:

import { exportToSvg } from "@excalidraw/excalidraw";

Self-hosting fonts

By default, Excalidraw downloads the fonts it needs from the CDN.

For self-hosting, copy the contents of node_modules/@excalidraw/excalidraw/dist/prod/fonts into the path where your app serves static assets, for example public/. Then set window.EXCALIDRAW_ASSET_PATH to that same path:

<script>
  window.EXCALIDRAW_ASSET_PATH = "/";
</script>

Demo

Try the CodeSandbox example.

Integration

Read the integration docs.

API

Read the API docs.

Contributing

Read the contributing docs.