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

@designless/annotate

v0.3.0

Published

Build-time source markers so Designless can route a rendered element back to its exact source line. Inert, dev-only, zero network. The only Designless code in your build.

Readme

@designless/annotate

Build-time source markers so Designless can route a rendered element back to its exact source line.

When you edit a rendered element on the Designless canvas, the edit needs to find its way home: to the (file, line) that produced it. This package stamps that provenance onto your host elements during development, as plain data attributes. That is all it does.

What it stamps

On each intrinsic host element (div, h1, button, custom elements), in development only:

<h1 data-source-file="src/page.tsx" data-source-line="12" data-selectable data-designless="annotate/v1">
  • data-source-file: repo-relative path (never absolute, never ..)
  • data-source-line: the element's source line
  • data-selectable: marks it selectable on the canvas (your own data-selectable is left untouched)
  • data-designless: the marker contract version

Components are skipped. Already-marked elements are skipped. That is the whole contract, and it is frozen at annotate/v1.

Two guarantees

  • Production is untouched. Markers are stamped in development only. Your production build is byte-for-byte what it would be without this package.
  • It cannot break your build. A marker it cannot produce is simply not produced. No code path here stops next dev or vite from starting.

Install

The one-liner does it for you:

npm create designless@latest -- next   # or: vite, svelte, vue, astro, qwik

Or wire it yourself.

Next.js (next.config.js), using the bundled SWC plugin (works under Turbopack):

const { withDesignless } = require('@designless/annotate/next')
module.exports = withDesignless({ /* your config */ })

Vite + React (vite.config.js):

import react from '@vitejs/plugin-react'
export default { plugins: [react({ babel: { plugins: ['@designless/annotate/babel'] } })] }

Svelte / SvelteKit (svelte.config.js):

import designlessAnnotate from '@designless/annotate/svelte'
export default { preprocess: [designlessAnnotate()] }

Vue (vite.config.js):

import vue from '@vitejs/plugin-vue'
import designlessVue from '@designless/annotate/vue'
export default { plugins: [designlessVue(), vue()] }

Astro (astro.config.mjs):

import { defineConfig } from 'astro/config'
import designlessAstro from '@designless/annotate/astro'
export default defineConfig({ integrations: [designlessAstro()] })

Qwik (vite.config.ts):

import { qwikVite } from '@builder.io/qwik/optimizer'
import designlessQwik from '@designless/annotate/qwik'
export default { plugins: [designlessQwik(), qwikVite()] }

Each engine reads the same frozen marker contract, so a stamped <div> looks identical no matter which framework produced it.

Scope

Development only. No network calls on any build path, no configuration, no change to production output. The package adds the marker attributes described above and nothing else.

Apache-2.0 · designless.app