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

elemenote

v0.23.0

Published

Embeddable annotation widget for live sites — global script or React/Next.js (elemenote/react). Pins, exports, MCP-friendly context. https://elemenote.io

Readme

elemenote

Elemenote is a human-first annotation layer for live web pages: pin elements, capture context, export notes, and hand structured briefs to coding assistants instead of re-describing the UI.

Use in development, not as a default production feature. Elemenote fits local dev, staging, and internal review (Design ↔ Engineering, QA, AI workflows). Shipping it to all production users adds UX, script weight, and annotation surface area—only do that when you intentionally want end users to see the widget.

Summary

Install

npm install elemenote

React: add peers (React 18 or 19):

npm install elemenote react react-dom

React

Styles live inside the widget (Shadow DOM). No separate CSS import.

import { Elemenote } from 'elemenote/react'

export function App() {
  return (
    <Elemenote
      position="bottom-right"
      appearance="system"
      locale="en-US"
    />
  )
}

Use an options object instead of flat props if you prefer; flat props override the same keys inside options. TypeScript: ElemenoteInitOptions, ElemenotePosition, ElemenoteAppearance, etc. from 'elemenote/react'.

Next.js (App Router)

Identity only (extension as editor): wrap next.config so the build writes data-elemenote-id and data-elemenote-name on each component host. You do not need <Elemenote /> on the page.

import { withElemenote } from 'elemenote/next'

export default withElemenote(nextConfig)

Development (next dev) also writes data-elemenote-src. Production writes id and name. { identity: 'off' } skips the attributes. { identity: 'path' } keeps the file path in production.

<!-- next dev -->
<section data-elemenote-id="a3f2c1b0d9e8" data-elemenote-name="Hero" data-elemenote-src="src/landing/Hero.tsx">
<!-- next build (default) -->
<section data-elemenote-id="a3f2c1b0d9e8" data-elemenote-name="Hero">

Export a .elemenote file and import it on the same origin + pathname. Collaborators need the Elemenote browser extension (or the widget below). Localhost and production keep the same host hash when the component path is the same; the file still will not apply across those different URLs.

elemenote/react is built as a Client Component ('use client'). You can still import Elemenote from app/layout.tsx if you want the widget in the page:

import type { Metadata } from 'next'
import { Elemenote } from 'elemenote/react'

export const metadata: Metadata = { title: 'My app' }

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return (
    <html lang="en">
      <body>
        {children}
        {process.env.NODE_ENV === 'development' && (
          <Elemenote position="bottom-right" appearance="system" />
        )}
      </body>
    </html>
  )
}

AI Settings

AI-related UI is off by default. Turn it on when you want the widget toolbar to show the AI settings control (MCP mode, bridge URL, CLI send provider, connection checks) and the AI Settings panel.

  • showAiSettings — set to true on <Elemenote> (or options.showAiSettings: true) to show the AI settings toolbar button and panel.
  • showAiSendButton — optional; set to true to show the floating “send to AI” control. You can enable either or both; enabling at least one turns on the AI feature surface in the widget.
import { Elemenote } from 'elemenote/react'

export function App() {
  return (
    <Elemenote
      position="bottom-right"
      appearance="system"
      showAiSettings
      showAiSendButton
    />
  )
}

License

Released under the MIT License. The full text is included in the tarball.

elemenote.io · MCP: elemenote-mcp