Weave Code
Psalm Toolkit Laravel Package
fp4php/psalm-toolkit
A toolkit of Psalm extensions and plugins for stricter, more accurate static analysis in PHP projects. Adds extra checks and type inference to catch bugs earlier, with configuration that fits into existing Psalm setups and CI pipelines.
fp4php/psalm-toolkit is a collection of utilities and extensions that make Psalm easier to adopt and maintain in PHP projects. It provides reusable configuration and helpers for stricter static analysis without repetitive setup.
- Ready-to-use Psalm configurations for common project layouts
- Helpers for building custom rules and issue handlers
- Type inference and stub utilities for cleaner analysis
- Simple integration with existing Composer workflows
Frequently asked questions about Psalm Toolkit
- What is fp4php/psalm-toolkit used for?
- fp4php/psalm-toolkit is a static-analysis toolkit for FP4PHP projects that use Psalm. It provides plugins, stubs, and configuration intended to help Psalm understand functional programming constructs in PHP. The goal is to catch type errors earlier and improve IDE feedback in FP4PHP codebases.
- How do I install fp4php/psalm-toolkit in a Laravel project?
- Install it with Composer as a development dependency, typically via composer require --dev fp4php/psalm-toolkit. Then wire the supplied Psalm plugins, stubs, and configuration into your project's psalm.xml so Psalm understands FP4PHP constructs. Check the package README and composer.json for the exact supported PHP, Psalm, and FP4PHP versions before adding it to a Laravel app.
- Does fp4php/psalm-toolkit work with Laravel applications?
- It can be used alongside Psalm in Laravel applications because it targets Psalm analysis of FP4PHP code. It does not replace Laravel-specific tooling; it adds FP4PHP-aware plugins, stubs, and configuration to your existing Psalm setup. Validate compatibility with your Laravel, PHP, and Psalm versions using the package's Composer constraints.
- What static analysis issues does fp4php/psalm-toolkit help catch?
- It helps Psalm understand FP4PHP types and functional programming constructs more accurately. That can surface mismatched type expectations and misleading IDE feedback earlier in development. The exact diagnostics depend on your Psalm configuration and how much FP4PHP code your project uses.
- Do I need FP4PHP installed to use fp4php/psalm-toolkit?
- Yes, the toolkit is designed for FP4PHP projects using Psalm. If you are not using FP4PHP, the plugins and stubs are unlikely to add much value. It is a static-analysis aid, not a runtime library that changes application behavior.
- How do I configure the toolkit's Psalm plugins and stubs?
- Add the toolkit's Psalm plugin entries to psalm.xml and point Psalm at any provided stub files as documented by the package. Keep that configuration in version control so local IDE analysis and CI use the same rules. Run Psalm after changing the configuration to confirm the plugins load correctly.
- Is fp4php/psalm-toolkit a replacement for Psalm?
- No. It is a toolkit that configures and extends Psalm for FP4PHP, so Psalm remains the static analyzer. In Laravel projects, you still need your normal Psalm setup and may also use Laravel-specific analysis tools. The toolkit only improves how Psalm handles FP4PHP constructs.
- Can fp4php/psalm-toolkit improve IDE feedback?
- Yes, by improving Psalm's understanding of FP4PHP constructs, it can lead to clearer type information and fewer false positives in editors that consume Psalm results. Actual IDE behavior depends on your editor integration and Psalm configuration. Re-run Psalm after configuration changes to confirm diagnostics improve.
- How should I use fp4php/psalm-toolkit in CI and production checks?
- Install it as a development dependency and run Psalm in CI with the toolkit configuration enabled. Cache Composer and Psalm caches for speed, and treat Psalm failures as build failures. Pin dependency versions in composer.lock so static-analysis results stay reproducible across environments.
- Is fp4php/psalm-toolkit maintained, and what are the alternatives?
- Check the package's Composer metadata, release history, and repository activity to confirm current maintenance, since those details are not included here. Alternatives include maintaining your own Psalm stubs and plugins for FP4PHP, using Psalm's built-in configuration directly, or relying on other static analyzers. For Laravel apps, Laravel-specific analysis tools can complement but not replace an FP4PHP-aware Psalm setup.
Weaver
How can I help you explore Laravel packages today?