@wolfstar/http-framework. They live outside this
repository, in wolfstar-project/plugins, and release on their own
schedule — adding one never bumps the core framework, and the framework has no required dependency on any of them.
Available Plugins
Browse the source on GitHub or the generated
API reference for the full surface of each one.
Installing a Plugin
/register entry point, imported before the client is created,
with configuration passed as a client option:
@wolfstar/plugin-i18next, @wolfstar/plugin-api, and
@wolfstar/plugin-subcommands-advanced.
Coming from @wolfstar/http-framework-i18n?
That package is deprecated in favor of @wolfstar/plugin-i18next. Follow the migration guide.
Writing Your Own Plugin
Plugins are regular@wolfstar/http-framework consumers — there is no separate plugin API to learn beyond the
client’s lifecycle hooks (preLoad, and the piece stores). Read an existing plugin’s source, such as
plugin-i18next, as a template, and
open a pull request against wolfstar-project/plugins to have it
added to this list.