- What is techpromux/base-bundle used for?
- Techpromux Base Bundle is described as the core for TechPromux bundles. It provides reusable base classes and shared configuration so developers can scaffold consistent Laravel/PHP applications faster and reduce repetitive setup across projects. It is intended as a foundational dependency rather than a complete feature package.
- How do I install techpromux/base-bundle with Composer?
- Install it with Composer by running composer require techpromux/base-bundle. Because it is a foundational package, it may also be pulled in automatically by other TechPromux bundles. After installation, check the package README for any service provider registration or configuration steps.
- Which Laravel versions does techpromux/base-bundle support?
- The provided package overview does not list specific Laravel or illuminate/support version constraints. Check the composer.json in the repository or the Packagist page for the exact framework requirements before installing. Match those constraints to your application's Laravel version to avoid dependency conflicts.
- Do I need to publish configuration files after installing techpromux/base-bundle?
- The overview mentions shared configuration, but it does not confirm whether configuration files are publishable. Look for a vendor:publish command or publish tag in the package README and service provider. If no publish step is documented, the package likely expects its defaults to be used or overridden through your application configuration.
- How does techpromux/base-bundle relate to other TechPromux bundles?
- It is described as the core for TechPromux bundles, so other packages in the TechPromux family may depend on it for shared base classes and configuration. You generally should not remove it when another TechPromux package requires it. Install the feature bundle you need and let Composer resolve base-bundle as a dependency.
- Can I use techpromux/base-bundle in an existing Laravel application?
- Yes, it can be added to an existing Laravel project with Composer, provided your Laravel version satisfies its dependency constraints. Since it provides foundational classes rather than a complete feature set, you will still need to build or install the application-specific functionality. Review the package source and README to confirm how its base classes should be extended.
- Is techpromux/base-bundle suitable for production use?
- The package is presented as a foundational core for TechPromux bundles, but the provided context does not include maintenance status, release history, or production guarantees. Before using it in production, review the repository's commit activity, tagged releases, issue tracker, and test coverage. Also confirm that its Laravel version constraints match your production stack.
- How do I test code that depends on techpromux/base-bundle?
- Test your application normally with Laravel's testing tools, such as PHPUnit or Pest, since base-bundle supplies reusable classes rather than a separate runtime. If you are testing the package itself, use a package testing harness such as Orchestra Testbench and check whether the repository includes its own test suite. Mock or extend the package's base classes as needed in your feature tests.
- What alternatives exist to techpromux/base-bundle?
- Alternatives depend on what you need: you can create an internal Composer package for shared base classes, use Laravel's built-in scaffolding and traits, or rely on package-development tools such as Orchestra Testbench for testing reusable code. If you want the TechPromux ecosystem, base-bundle is the intended foundation. Compare maintenance, documentation, and Laravel version support before choosing.
- How actively is techpromux/base-bundle maintained?
- The provided context does not include release cadence or maintainer details. Check the GitHub repository for recent commits, tagged versions, open issues, and Packagist release history. Pin a known version in composer.json and review changelogs before upgrading.