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

@clicktocode/angular

v0.3.3

Published

Click an element in your running Angular app and hand it to a coding agent — element picker + OpenCode bridge.

Readme

@clicktocode/angular

Click an element in your running Angular (17+) app and hand it to a coding agent. Full docs →

Hold Alt (⌥ Option on Mac), click an element — or -click to select several — then type what you want. Your agent gets the element's exact DOM and its component stack (names + inputs), so it doesn't burn tokens searching the codebase for it. No agent set up? With no adapter configured the picker just copies — click one element (or ⇧-click several) and paste the context into any AI chat.

Easiest setup — let your AI do it: give your coding agent the repo's SKILL.md and say “integrate clicktocode into this project” — it detects your framework, installs the right package, and wires up the agent of your choice.

npm i -D @clicktocode/angular

Angular has no Vite config, so start the bridge alongside ng serve and load the picker in main.ts:

// package.json — `clicktocode` is the bridge CLI (from @clicktocode/core)
"scripts": { "dev": "npx clicktocode & ng serve" }
// main.ts — after bootstrapApplication(...)
import { isDevMode } from "@angular/core";
import { clickToCode, opencodeAdapter } from "@clicktocode/angular";
if (isDevMode()) {
  clickToCode({ adapter: opencodeAdapter({ serverUrl: "http://127.0.0.1:6567" }) });
}

The snippet above wires OpenCode.

Component stack is read from window.ng (dev-only). You get real component names and @Input() props — but Angular exposes no source file at runtime, and the stack is empty in production. Needs OpenCode: npm i -g opencode-ai@latest && opencode auth login (or use clipboardAdapter()).

Built on @clicktocode/core. MIT.