Ramonda

Reference

The pages you arrive at with a name in hand. Nothing here teaches a concept; each one answers what is this, exactly about something you already met.

By name

  • API — every export in every package, with what it is for. Start here when you have seen a name and do not know which package it came from.
  • Every decorator, at a glance — the table: which run on the client, the server or both, which work on a hook, and which may be declared twice. Each decorator also has its own page.

When something is reported

  • Diagnostics — every code the framework can report while running, and what to write instead. One page per code, so RMD003 is an address rather than a search.
  • Rules — every check ramonda-check proves from your source, before anything runs. Also one page each.

Around the code

  • Checking your app — how to run the checker, what it proves that a running page cannot, and the graph it builds on the way.
  • Configuring your build — the bundler settings the decorators need, as a Vite plugin, as esbuild options, or as the settings themselves.
  • Upgrading — what a version number promises before 1.0, why a minor can break you, and how to move between versions on purpose rather than by surprise.

Next

  • API — if you have a name.
  • Diagnostics — if you have a code.
  • Core concepts — if what you actually want is the model behind the name.