Add-on limitions
As of the current version of Nova 3, add-ons do not have any mechanisms to replace view files like Nova 2. This was an intentional decision to simplify the add-on architecture at the start. Depending on interest level, we may introduce new tools and mechanisms in the future. If you are interested in injecting content into various view files, you can check out the documentation about render hooks.
Directory structure
- Migrations
- Providers
- AddonServiceProvider.php
- addon.json
- Addon.php
Service provider
Every add-on created through Nova includes a service provider that will be registered during Nova's request cycle. Service providers are a central place to register services into the container, setup event listeners, and much more. The add-on's service provider is where you can do all of your setup for the add-on to run properly or extend Nova as needed.
class AddonServiceProvider extends BaseAddonServiceProvider{ protected string $location = 'PostArchiver'; public function boot() { Event::listen(PostPublished::class, fn () => $sendToGoogle->send()); }}The boot() method is called during each Nova request and is the place to ensure that anything you need done to make your add-on work is done.
Note: in order to make add-on service providers as hands-off as possible, you will not be able to do any work in a register() method like you would in a normal Laravel application. Any work you want to do will have to be done in the boot() method.