Weave Code
Laravel Paket Laravel Package
cybercog/laravel-paket
Laravel Paket is a package-management toolkit for Laravel that helps you create, organize, and maintain reusable packages or modules inside your application. It keeps code modular and maintainable, making it easier to extend projects and share components across Laravel apps.
Composer GUI. Manage Laravel dependencies from web interface without switching to command line!
Frequently asked questions about Laravel Paket
- What is Laravel Paket used for?
- Laravel Paket is a Composer GUI for Laravel applications: it gives you a web interface for managing your project's Composer dependencies without switching to the command line. Instead of running composer require or composer update in a terminal, you work from a browser screen inside your Laravel app. It is aimed at developers who want a visual, app-native way to inspect and change installed packages during development.
- How do I install cybercog/laravel-paket?
- Install it with Composer using composer require cybercog/laravel-paket, which resolves the latest 1.x release such as ^1.9. Laravel's package auto-discovery should register the service provider, but verify this in your composer.json if you have discovery disabled. After installing, publish any config or assets the package ships with and open the route it registers to reach the interface. Confirm the exact PHP and illuminate/* constraints in the installed version's composer.json before you commit.
- Which Laravel versions does Laravel Paket support?
- Release 1.9.0 is the first version to add PHP 8 support, which implies earlier 1.x releases were capped at PHP 7.4 and therefore effectively limited to Laravel 8 or older. Because Laravel 9 needs PHP 8.0, Laravel 10 needs 8.1, and Laravel 11 needs 8.2, you should check the actual illuminate/support constraint in the tag you install rather than assume compatibility. Treat the changelog line as a starting point and confirm with a real install on your target framework version.
- Does Laravel Paket work on PHP 8.1, 8.2 and 8.3?
- The changelog only records that PHP 8 support was added in 1.9.0, which typically means CI passes on PHP 8.0 rather than full coverage of every 8.x release. On 8.1 and later you may hit deprecation notices from internal function signature changes, and those can be promoted to exceptions under stricter error handling. Before relying on it, run the package with error_reporting set to E_ALL on your exact PHP version with APP_DEBUG both on and off.
- Is it safe to run Laravel Paket in production?
- No, you should not expose a Composer GUI on a production site. The interface can trigger dependency operations that rewrite composer.json and composer.lock, run third-party install scripts, and leave the application in a broken state mid-request. Keep it enabled only in local or isolated staging environments, and gate it behind middleware and authorization even there. Treat it as a developer tool, not an application feature.
- How do I restrict access to the Laravel Paket web interface?
- Protect the routes with your existing auth middleware plus a gate or ability check that only your developer accounts pass. Add an environment check so the provider or routes are only registered when APP_ENV is local, and consider an IP allowlist or a VPN-only binding if the environment is shared. Never leave the interface reachable on a publicly resolvable host without authentication in front of it, since anyone who reaches it can alter your dependency tree.
- Does Laravel Paket need shell access or process execution on the server?
- Managing dependencies from a web interface generally requires the package to invoke Composer, which means the PHP process must be allowed to execute external commands and write to composer.json, composer.lock and vendor. Many shared hosts and hardened PHP-FPM setups disable those functions or make vendor read-only, so verify this before adopting the package. If process execution is blocked, the GUI cannot complete installs even if the pages render correctly.
- What can I actually do from the Paket interface?
- The intent is to let you inspect installed packages and run dependency operations such as requiring, updating or removing packages from the browser instead of the terminal. Exact capabilities depend on the release you install, and the published changelog for 1.9.0 mentions only PHP 8 support, so do not assume features beyond what the README and source show. Test the specific actions you need, especially removals and updates, in a disposable checkout before trusting them on a real project.
- Is Laravel Paket actively maintained, and will there be a Laravel 11 compatible release?
- There is little public signal to rely on: the 1.9.0 changelog is a single line noting PHP 8 support from one numbered pull request, which suggests a small maintainer group and possibly an external contribution. Check the commit cadence, age of open issues, and whether the release has a CI matrix covering 8.0 through 8.3 before you depend on it. If you need Laravel 10 or 11 support today, plan for the possibility that no aligned major release arrives and keep the Composer CLI as your fallback.
- What are the alternatives to Laravel Paket?
- The default alternative is the Composer CLI itself, which is always in sync with your constraints and never needs write access from a web process. IDE integrations in PhpStorm and VS Code also surface installed packages and available updates, and general Composer GUIs exist outside the Laravel ecosystem. If your real goal is modular code rather than dependency management, consider first-party Laravel package conventions or a dedicated modularity package instead.
Weaver
How can I help you explore Laravel packages today?