- Is oneup/contao-developer-convenience-bundle a Laravel package?
- No. It is a Contao CMS bundle, and Contao is a Symfony-based application with its own bundle system, DCA configuration model, and template engine. It does not use Laravel service providers, Artisan commands, or Eloquent conventions, so there is no Laravel integration layer to hook into.
- Can I install oneup/contao-developer-convenience-bundle in a Laravel application?
- Composer may technically install it, but it provides no Laravel features, service providers, or Artisan commands. Its dependencies target Contao and Symfony internals, so you should expect version conflicts with modern PHP and Symfony constraints. The practical value for a Laravel codebase is effectively zero.
- What does the Contao developer convenience bundle actually do?
- It adds opinionated developer helpers and shortcuts intended to speed up Contao extension development. That typically includes convenience console commands, debug facilities, and boilerplate-reducing utilities for common backend tasks. The package description explicitly warns that it is highly opinionated and used at your own risk.
- Which Contao versions does this bundle support?
- The repository is archived and does not advertise active support for modern Contao releases. Its composer.json constraints likely target older Contao 3.x or early 4.x lines and predate current PHP 8.x requirements. You must verify the PHP and Contao version floor before considering any use, and assume Contao 4.13 or 5.x compatibility is not guaranteed.
- Is oneup/contao-developer-convenience-bundle still maintained?
- No. The repository lives under the 1up-lab-archive organization, has roughly five stars and zero dependents, and has no active maintainer. Upstream is frozen, so no security patches, PHP compatibility fixes, or Contao API updates will ever land. Treat any adoption as a permanent internal maintenance commitment.
- What are the risks of enabling this bundle in production?
- Developer-convenience bundles often register console commands and debug endpoints, which are dangerous if accidentally enabled outside local development. The package is abandoned, so API drift against newer Contao and Symfony versions may cause runtime failures. It also has no upstream security response process, leaving any discovered issue unpatched.
- How do I install the bundle in a Contao project?
- Use Composer with the dev flag, for example composer require --dev oneup/contao-developer-convenience-bundle, then register the bundle according to your Contao version. Before doing so, inspect the composer.json PHP and Contao constraints and run a smoke test on your exact target version. Restrict it to development environments and keep it out of production builds.
- Should I fork the bundle or reimplement its features?
- Reimplementation is usually the better choice for an archived package with five stars and zero dependents. Read the bundle as documentation, identify the two or three genuinely useful commands or helpers, and rebuild them natively for your Contao version. If you must fork, vendor it under an internal namespace, pin constraints, audit file-writing and cache-clearing commands, and document it as unsupported by upstream.
- Does the bundle work with PHP 8.1 or newer and Symfony 5 or 6?
- Probably not without changes. The archived composer.json almost certainly predates PHP 8.x and may conflict with Symfony 5 or 6 major versions. Run static analysis and a smoke test on your target stack rather than trusting the README. If conflicts appear, there is no upstream maintainer to patch them for you.
- What should Laravel developers use instead of this Contao bundle?
- Laravel developers should use Laravel-native tooling such as Artisan commands, Laravel Telescope, Laravel Debugbar, and package-specific dev helpers. This bundle has no equivalent role in a Laravel application because it depends on Contao's DCA model and bundle APIs. If your team is evaluating it for a Laravel project, the correct outcome is to redirect scope rather than adopt it.