- What does laravel-plus/extension actually do?
- It adds a lightweight extension (add-on) architecture on top of Laravel 5, letting you organize features into discoverable modules rather than scattering them across the app. Each add-on can register its own services and routes, so plugin-style functionality stays isolated from core application code. Think of it as a foundation for modular, maintainable Laravel applications rather than a domain library.
- Which Laravel and PHP versions does laravel-plus/extension support?
- The package was built for the Laravel 5 era, so its illuminate/* constraints are likely pinned to 5.x and possibly 6.x. It will not resolve cleanly against modern Laravel releases without constraint overrides, which are not recommended. Always read the declared constraints in composer.json and run a compatibility matrix against your target Laravel and PHP versions before doing anything else.
- How do I install laravel-plus/extension with Composer?
- The expected path is a standard composer require laravel-plus/extension, most likely relying on Laravel package auto-discovery, possibly with a published config file or facade alias. Install it in a throwaway Laravel 5 project first so you can inspect exactly which service providers, aliases, and global helpers it registers. Because the repository is archived, expect to pin the version explicitly if you proceed at all.
- Is laravel-plus/extension still maintained?
- No. The repository is archived, which means no security patches, no compatibility updates for newer Laravel or PHP releases, and no issue triage. It has roughly 55 stars and zero dependents, so there is no ecosystem validation or public evidence of production use at scale. Treat it as a source of ideas or extraction candidates rather than a live dependency.
- Can I use laravel-plus/extension with Laravel 10 or 11?
- Almost certainly not out of the box, since the illuminate/* constraints target the Laravel 5/6 era and will fail to resolve. Forcing constraint overrides with --ignore-platform-reqs or inline aliases is a bad idea for a package this stale, because boot behavior and internal APIs have changed substantially since then. If you only want a handful of utilities, extract them into your own namespace instead of fighting the dependency graph.
- How does laravel-plus/extension register extension routes and service providers?
- The extension system is designed so each add-on ships its own service provider and routes, keeping registration local to the module instead of in a central bootstrap file. The exact conventions should be verified directly in the source, because service-provider boot behavior is not well documented. That lack of documentation is one of the practical risks: magic registration is hard to debug when it misbehaves.
- Is laravel-plus/extension safe to use in production?
- The technical risk is high and concentrated in lifecycle rather than code quality. An archived package means no security patching, no compatibility updates, and no triage, plus secondary risks such as abandoned transitive dependencies and undocumented boot behavior. The recommended posture is not to adopt it as a runtime dependency and to require a documented audit before copying any code in.
- Does laravel-plus/extension register global helpers or macros that could collide with my application code?
- That is one of the flagged risks for this kind of helper-layer package, since global functions, facade aliases, and macros expand the blast radius from a single import to the entire application surface. The README excerpt does not enumerate them, so you must audit the source and the service provider to see exactly what gets registered globally. If you extract code, drop the global helpers and namespace anything you keep.
- What are the alternatives to laravel-plus/extension for modular Laravel apps?
- For most teams, first-party primitives are enough: Composer path repositories, Laravel package auto-discovery, and well-scoped service providers cover modular registration without a third-party layer. If you want a batteries-included module system, actively maintained options such as nwidart/laravel-modules have real ecosystem validation. Another low-risk route is an internal package under your own vendor namespace with tests you own.
- Can I fork laravel-plus/extension or extract code from it?
- Yes. It is MIT licensed, so forking, modifying, and source extraction carry no legal friction. The preferred path is source extraction: identify the few utilities you actually need, copy them into app/Support or an internal package, add tests, and own them outright. A full internal fork is only justified if the useful surface area is large, and either way you need a named internal maintainer of record.