Weave Code
Psalm Laravel Nova Laravel Package
interaction-design-foundation/psalm-laravel-nova
Psalm plugin for Laravel Nova that improves static analysis by providing accurate type information and stubs for Nova resources, fields, actions, and filters. Helps catch errors earlier and reduces false positives in Psalm checks.
🚠 Psalm plugin for Laravel Nova
Frequently asked questions about Psalm Laravel Nova
- What is interaction-design-foundation/psalm-laravel-nova used for?
- It is a Psalm plugin for Laravel Nova projects that supplies stubs and type information for Nova resources, fields, actions, filters, and related APIs. Its purpose is to help Psalm understand Nova's dynamic and fluent APIs, reducing false positives and improving autocompletion and refactoring confidence. It is developer tooling only, intended for require-dev, with no runtime footprint in production.
- How do I install psalm-laravel-nova in a Laravel Nova project?
- Install it as a dev dependency with composer require --dev interaction-design-foundation/psalm-laravel-nova, then register the package's plugin class in psalm.xml and run vendor/bin/psalm. For meaningful analysis you need a working Laravel Nova installation, which is commercial and requires licensed Composer credentials. Because the package is pre-1.0, pin the version explicitly rather than relying on a floating constraint.
- How do I register the Psalm Laravel Nova plugin in psalm.xml?
- Add the plugin class documented by the package to the plugins section of your psalm.xml, then run Psalm as usual. The package is designed for simple registration in psalm.xml, but the exact class name and any supported configuration should be taken from the README for your pinned version. After registration, verify that Nova-related false positives actually decrease in your codebase.
- Does this package work with PHPStan or Larastan?
- No. It is a Psalm plugin only and does not provide PHPStan or Larastan integration. If your Laravel team has standardized on PHPStan with Larastan, this package has no path into that analyzer setup. It only makes sense for projects that have already chosen Psalm.
- Which Laravel, Nova, PHP, and Psalm versions are supported?
- Compatibility is a tight matrix of Laravel Nova major version, Laravel version, PHP version, and Psalm version, and the provided overview does not document a full support table. Nova is closed source, so plugin authors must model its internals and compatibility can shift between Nova majors. Test the plugin against your exact versions in CI and pin a known-good release.
- Do I need Laravel Nova credentials for CI when using this plugin?
- Yes, if your CI job resolves a real Laravel Nova installation, you must provide Nova license credentials such as NOVA_USERNAME and NOVA_PASSWORD or an equivalent license key as secrets. Nova is distributed through nova.laravel.com behind licensed Composer credentials, so this is an ops and procurement dependency rather than a code dependency. The plugin itself is require-dev and has no production runtime coupling.
- What Nova APIs does psalm-laravel-nova actually cover?
- The v0.2.3 fixes show modeling for callback paths on Actions, Filters, Lenses, and Fields, including canSee callbacks accepting a NovaRequest and Field::make resolve callbacks accepting typed resource or attribute arguments. Coverage for resources, metrics, lenses-as-classes, and custom field types beyond those paths is not demonstrated in the provided context. Because Nova is closed source, you should read the stubs and plugin hooks to verify coverage for your own Nova usage.
- Is version 0.2.3 stable enough for production use?
- It is a pre-1.0 patch release, so treat it as usable but not API-stable. The 0.2.3 release contains no breaking changes or deprecations, and upgrades within 0.2.x should be low risk, but 0.x semantics mean the plugin class or configuration surface could change before 1.0. Pin the version explicitly and review release notes before upgrading.
- How does this compare with Psalm's Laravel plugin or PHPStan and Larastan?
- This package is specialized for Laravel Nova's dynamic APIs, while Psalm's general Laravel plugin targets Laravel core behavior and does not necessarily model Nova internals. PHPStan with Larastan is the more common Laravel static-analysis stack, but this package does not integrate with it at all. If you use Psalm and Nova heavily, compare actual stub coverage against your code; if you use PHPStan, this package is not an alternative.
- How is psalm-laravel-nova maintained, and what if it is abandoned?
- The project has signals of active triage, including a v0.2.3 fix release with named human authorship and Renovate bot activity, but it has low adoption with about 2 stars, 0 dependents, and single-org provenance from InteractionDesignFoundation. It may quietly go stale if the maintainer stops using Nova or migrates analyzers, which could produce false confidence rather than loud failures. The MIT license makes fork-and-maintain legally clean, and pinning versions plus monitoring releases limits surprise risk.
Weaver
How can I help you explore Laravel packages today?