Official plugins
A plugin's only job is to extend the Pilet API, and plugins live only in the app shell — see PiralPlugin for what that means. Each plugin below adds typed methods to the api object every pilet receives; none of them is required to have a capability, they just expose it to pilets.
There are two tiers of official plugins:
- Standard plugins — bundled in the
piral-extpackage, which ships as part of the all-in-onepiralpackage. If you scaffolded withpiral, these are already available. - Additional official plugins — developed and published from the Piral monorepo but installed individually. Add them when you need them (and register them explicitly on
piral-core).
Install a plugin in the app shell and add its factory to createInstance({ plugins: [...] }). Each plugin then surfaces its methods on PiletApi, fully typed.
Standard plugins
These ship in piral-ext and are included with the piral package. On piral-core, install and register the ones you want.
Additional official plugins
All of these are official (developed in the Piral monorepo); install and register them as needed.
App & UX features
Data access
Authentication
As described in PiralPlugin, these plugins exist purely to bring tokens (and related helpers) to the Pilet API. You do not need any of them to implement authentication — the app shell can authenticate on its own. Add one only when pilets should consume tokens through the API. See Authentication.
State & performance
Framework converters
Converters let a pilet be written in a framework other than React. A converter is not installed as a shell plugin — the pilet imports it from the converter's standalone /convert submodule (e.g. piral-svelte/convert) and wraps its components with the matching from… helper. See Multi-framework pilets and Creating a converter.
Plain web components need no converter — a custom element is already a DOM element, so it can be used directly.
Tooling packages (not Pilet API plugins)
Some official piral-* packages are not Pilet API plugins and don't belong in createInstance:
- Bundler & CLI plugins —
piral-cli-webpack5,piral-cli-esbuild,piral-cli-rspack,piral-cli-vite,piral-cli-parcel2,piral-cli-xbuild, plus helpers likepiral-cli-local-feedandpiral-cli-dotenv. These extend the CLI; see the CLI reference. - Utility libraries — e.g.
piral-ssr-utils,piral-hooks-utils,piral-systemjs-utils. These are plain helper libraries you import where needed.
Finding the complete, current list
New plugins are added over time. The authoritative, always-up-to-date list is the src/plugins and src/converters folders in the Piral monorepo, and the piral-* packages published on npm.