agentleFS
Sign inStart free
CloudflareKnown publishercloudflare/workerd/src/per_isolate/events/AGENTS.md

workerd / events

AGENTS.md9.1k starsChanged 8 months agoApache-2.0View on GitHub

EventTarget plumbing for the bootstrap. Parent directory conventions (primordials discipline, private-brand dispatch, no instanceof) apply; see src/per_isolate/AGENTS.md. - A bootstrap EventTarget subclass extends EventTarget from events/event-target-internals and reaches EventTarget internals only through that module, never through utils or the EventTarget primordial directly. EventTarget itself is still C++; when it moves to the bootstrap, the module is reimplemented over it and subclasses are untouched. - Listener-count hooks run synchronously inside addEventListener(), removeEventListener() and dispatch: they must neither run user code nor…

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 3 mentionsFeb 2026: 0 mentionsMar 2026: 2 mentionsApr 2026: 3 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 6 mentionsSep 2026: 4 mentionsOct 2026: 4 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the cloudflare/workerd repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about cloudflare/workerd

The biggest 5 of 39 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 39

Talked about on GitHub, Bluesky, Hacker News and Stack Overflow (39 times).

On GitHub · 32

27 more on GitHub

On Hacker News · 2

On Stack Overflow · 1

The file

Create a free account to mount
Files
AGENTS.md

src/per_isolate/events/

EventTarget plumbing for the bootstrap. Parent directory conventions (primordials discipline, private-brand dispatch, no instanceof) apply; see src/per_isolate/AGENTS.md.

FILE MAP

FileRole
event-target-internals.tsThe seam every bootstrap EventTarget subclass goes through to reach the EventTarget it extends: the base class, listener-count hooks, on<type> handler attributes, dispatch with an explicit exception policy, and trusted event creation. The contract is in the file header.

KEY RULES

  • A bootstrap EventTarget subclass extends EventTarget from events/event-target-internals and reaches EventTarget internals only through that module, never through utils or the EventTarget primordial directly. EventTarget itself is still C++; when it moves to the bootstrap, the module is reimplemented over it and subclasses are untouched.
  • Listener-count hooks run synchronously inside addEventListener(), removeEventListener() and dispatch: they must neither run user code nor throw.
  • Events the runtime fires are dispatched through the module's dispatchEvent(), with the policy from effectiveExceptionPolicy(), as C++ subclasses use dispatchEventImpl(). The public dispatchEvent() is for user-constructed events.
  • A subclass that replaces a C++ class gets a parity suite under src/tests/events/<api>/, run against both implementations; see src/tests/events/AGENTS.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free