Filament Skeleton Laravel Package

Getting Started

• Confirm the package supports Filament 4.x and your Laravel/PHP versions before installing. Since 2.0.0 is the first Filament 4-compatible release, treat it as a major upgrade rather than a patch.
• Install with Composer using the package’s documented name, then run the standard Filament asset/publish steps if the package ships config, views, migrations, or assets:

  composer require <vendor>/<package>:^2.0
  php artisan vendor:publish --tag=<package-config>
  php artisan filament:assets
  

• Look first at:
  1. The package README/upgrade guide for the 1.x → 2.x changes.
  2. The package service provider and Filament plugin class.
  3. The example panel provider registration in the docs.
• First use case: register the plugin on a Filament panel, then apply its resource/page/form/table integration to one model or resource in a development environment before rolling it out.

  use Vendor\Package\PackagePlugin;
  
  public function panel(Panel $panel): Panel
  {
      return $panel
          ->plugin(PackagePlugin::make());
  }
  

• If the package exposes traits, interfaces, or base resource classes, start with a single Filament resource and verify the generated UI, authorization, and persistence behavior before applying it broadly.

Implementation Patterns

• Panel-level registration: Most Filament plugins are enabled per panel via ->plugin(...). Keep registration in each PanelProvider where the feature should appear, rather than globally, so multi-panel apps remain predictable.
• Resource integration: If the package provides traits, interfaces, or base classes, apply them to one resource first. Check that form/table schema methods, authorization, and record resolution still behave as expected under Filament 4.
• Configuration-driven behavior: Publish the config file and keep environment-specific settings in .env or config files. Avoid editing vendor-published views directly; override them in your app’s resource/view layer where supported.
• Composition over inheritance: Where the package offers closures, callbacks, or builder methods, prefer composing behavior in your PanelProvider, resource, or page classes instead of forking package code.
• Upgrade workflow: For existing apps moving from Filament 3, upgrade Filament first, then the package, then run composer update, clear caches, and re-publish assets. Test one panel and one resource before expanding.
• Multi-panel apps: Register the plugin only on panels that need it. Verify navigation groups, permissions, and tenant scoping per panel.
• Testing: Add at least one feature test that boots the panel and renders the package’s page/resource. This catches namespace, asset, and registration regressions early.

Gotchas and Tips

• Major version alignment: 2.0.0 is explicitly the Filament 4 release. Do not assume it is compatible with Filament 3, and do not mix Filament 3 and 4 packages in the same app.
• Namespace shifts in Filament 4: Filament 4 renamed/moved several concepts compared with v3, especially around forms/schemas. If the package docs show older imports, verify against the installed package source.
• Asset and view caches: After upgrading, run:

  php artisan optimize:clear
  php artisan filament:assets
  

  Stale published assets are a common cause of “plugin installed but UI missing” issues.
• Publish tags can change: A major release may rename or remove publish tags. Check php artisan vendor:publish --help output or the package service provider before assuming old tags still work.
• Config drift: Compare your published config with the package’s new default config. New options may be required, and removed options may silently do nothing.
• Plugin registration debugging: If the plugin does not appear, verify the panel provider is actually loaded, the plugin is registered on the correct panel, and the class namespace matches the installed version.
• Extension points: Prefer the package’s documented hooks, closures, and view overrides. If you must extend internals, pin the package version and add tests around the extended behavior.
• Check the upgrade guide before production: Because this is the first Filament 4 release, expect breaking changes from any prior 1.x line even if the release note is short. Review the changelog, composer constraints, and any migration notes before upgrading production apps.