- How do I install irazasyed/larasupport in a Lumen application?
- Install it with Composer using composer require irazasyed/larasupport, then register the package service provider in your Lumen bootstrap/app.php file. Larasupport is designed for Lumen and adds Laravel-style helpers, package service-provider registration, config publishing, and Artisan commands. After registering it, run your normal package-discovery and config-resolution smoke tests. For version 1.7.1, treat the upgrade as a revert to pre-regression config_path() behavior rather than a new feature.
- Do I need Larasupport in Laravel, or only in Lumen?
- Larasupport is an adapter layer for Lumen, not a replacement for Laravel. It backports Laravel-style helpers and package conveniences so Laravel-oriented third-party packages can run in lightweight Lumen services. In an all-Laravel estate the package is unnecessary dead weight. Use it only when a Lumen service consumes vendor packages that assume Laravel helpers such as config_path() exist.
- What does the vendor:publish Artisan command add to Lumen?
- Larasupport adds the Laravel-style vendor:publish Artisan command to Lumen so you can publish package configuration and other vendor assets into your application. This matters when a Laravel package expects its config file to be published before it boots or merges settings. The command is part of Larasupport's package-support layer, alongside service-provider registration and helper backports. Test publishing in a non-production branch because misresolved config paths can silently fall back to package defaults.
- Which PHP and Lumen versions does irazasyed/larasupport support?
- The package is Composer-installable and targets Lumen with Laravel-compatible helper semantics, but you should verify its PHP version floor and supported Lumen major versions in composer.json before bumping. Version 1.7.1 is a patch-level revert that adds no new public API or configuration changes. Diff config_path() output against your current pinned version in a scratch service rather than relying on a changelog line. Compatibility acceptance is behavioral equivalence with the version you last validated.
- What changed in Larasupport 1.7.1 for config_path()?
- Version 1.7.1 reverts config_path() behavior and references upstream issues #23 and #24, so it restores the pre-regression semantics consumers previously relied on. There is no new public API, no deprecation, and no configuration change. If you ran the affected prior release, treat 1.7.1 as a corrective hotfix. If you skipped that release, the bump is routine dependency hygiene.
- Can Larasupport helper functions collide with native Lumen helpers?
- Helper-function collisions are a latent risk because Larasupport defines global Laravel-style helpers that Lumen does not natively provide. If a future Lumen release ships native equivalents such as config_path(), loading both implementations can cause redeclaration errors or ambiguous behavior. Treat Lumen upgrades as compatibility events and check for duplicate helper definitions before rolling out. Keep the package pinned so an upstream helper change cannot surprise production.
- How should I test a Larasupport upgrade before production?
- Inventory services that require Larasupport through your Composer dependency graph, then reproduce config_path() output on your current pin versus 1.7.1 in a non-production branch. Upgrade one low-traffic service first and run config-resolution and package-discovery smoke tests. Confirm that no packages fall back to hardcoded or default configuration in logs, because that failure mode is silent. Roll to remaining services only after behavioral equivalence is proven.
- Is Larasupport safe to run in production?
- It has a small code surface and installs as a single service provider, but it is a community project with a single maintainer and infrequent releases. The main production risk is silent failure: a misresolved config_path() can make packages use hardcoded defaults instead of throwing a boot error. Pin an explicit version, assign an internal owner, and monitor upstream issues #23 and #24. Budget a small recurring maintenance allowance rather than assuming zero support cost.
- What are alternatives to using Larasupport in Lumen?
- The cleanest alternative is moving the service to Laravel, where these helpers and package conventions are native and Larasupport is dead weight. If you must stay on Lumen, you can manually register package service providers and copy or merge config files yourself, though that recreates what Larasupport automates. A maintained internal fork is another option if upstream goes dormant or you need a specific config_path() behavior. Choose based on how many Laravel-first vendor packages your Lumen service actually consumes.
- Should I pin irazasyed/larasupport to an exact version?
- Yes, an explicit pin or a tightly controlled constraint is prudent for a single-maintainer community shim. Caret ranges invite unplanned config_path() regressions, and the 1.7.1 revert shows why helper resolution semantics deserve deliberate review. Keep the dependency pin visible in your internal dependency register and document the validated Lumen and PHP versions. If upstream becomes dormant, plan for an internal fork or patch strategy.