Weave Code
Ide Stubs Laravel Package
phalcon/ide-stubs
phalcon/ide-stubs provides up-to-date IDE stubs for the Phalcon PHP framework, enabling autocompletion, type hinting, and code navigation in editors like PhpStorm. It helps developers explore Phalcon classes and methods with accurate metadata and no runtime dependency.
Phalcon IDE Stubs
Frequently asked questions about Ide Stubs
- What is phalcon/ide-stubs used for?
- It provides IDE stubs for the Phalcon PHP framework, enabling autocompletion, type hints, and code navigation in editors like PhpStorm. It is a development-only dependency with no runtime impact. It is not designed for Laravel applications.
- Can I use phalcon/ide-stubs in a Laravel project?
- No, it is not recommended. The stubs target Phalcon namespaces and APIs, which are incompatible with Laravel's Illuminate components and autoloading. Adding them to a Laravel project can cause namespace conflicts and false positives in your IDE. Use Laravel-specific tools like Laravel IDE Helper or Barrel instead.
- How do I install phalcon/ide-stubs?
- Install it as a dev dependency via Composer: composer require --dev phalcon/ide-stubs. Then configure your IDE to include the stub directory, typically vendor/phalcon/ide-stubs. No Laravel service provider or configuration is needed because it is not a Laravel package.
- Does phalcon/ide-stubs support Laravel versions?
- It does not target Laravel at all, so Laravel version support is not applicable. The package tracks Phalcon framework versions and their class signatures. For Laravel version-specific stubs, use Laravel IDE Helper or PHPStan with Laravel extensions.
- Is phalcon/ide-stubs a replacement for Laravel IDE Helper?
- No. Laravel IDE Helper generates stubs for Laravel facades, models, and container bindings, while phalcon/ide-stubs only covers Phalcon classes. They serve different frameworks and should not be mixed. Laravel developers should rely on Laravel IDE Helper, Barrel, or similar Laravel-focused tools.
- Will phalcon/ide-stubs cause conflicts with Laravel facades in PhpStorm?
- Yes, it can. Phalcon stubs may introduce Phalcon namespaces and class signatures that your IDE might try to resolve alongside Laravel's Illuminate classes. This can lead to false autocompletions or type errors. Isolate the stubs or avoid them in Laravel projects.
- Can I use phalcon/ide-stubs for static analysis with PHPStan in a Laravel app?
- It is not recommended for Laravel static analysis. PHPStan with Larastan or Laravel-specific extensions is the appropriate choice. Phalcon stubs would add irrelevant symbols and potentially increase false positives. Only use them if you have legacy Phalcon code in a separate analysis environment.
- What are alternatives to phalcon/ide-stubs for Laravel autocompletion?
- For Laravel, use barryvdh/laravel-ide-helper, Barrel, or PHPStan with Larastan. These tools generate accurate stubs for Laravel facades, models, and container bindings. They integrate with Laravel's autoloader and are actively maintained for current Laravel versions.
- Is phalcon/ide-stubs maintained and safe for production?
- It is a development-only package with no runtime dependency, so it does not affect production code. Maintenance follows Phalcon releases, not Laravel. For production Laravel apps, it is unnecessary and should be kept out of your runtime dependencies.
- When would a Laravel developer ever need phalcon/ide-stubs?
- Only in niche cases, such as migrating a legacy Phalcon codebase to Laravel and needing temporary IDE support for old Phalcon files. Even then, keep the stubs isolated from your Laravel application and IDE workspace. For new Laravel projects, use Laravel-native tooling instead.
Weaver
How can I help you explore Laravel packages today?