- What is mikoweb/vsymfo-core used for?
- It is the shared foundation for the VSymfo package ecosystem, bundling reusable Laravel service providers, centralized configuration and publishing support, and common contracts, helpers, and utilities. You typically pull it in when you use or build VSymfo components so they stay consistent instead of duplicating boilerplate. Standalone Laravel applications can use it too, but its main purpose is composing VSymfo packages.
- How do I install mikoweb/vsymfo-core with Composer?
- Install it with composer require mikoweb/vsymfo-core. Laravel's package auto-discovery should register the bundled service providers automatically, so you usually do not need to edit config/app.php. If you have disabled discovery, register the providers listed in the package's composer.json extra section manually.
- Do I need to require mikoweb/vsymfo-core in every VSymfo project?
- Usually not directly, because the VSymfo packages that build on it declare it as a dependency and Composer installs it for you. If you are developing your own package on top of the VSymfo foundation, add it explicitly to your require section. Check the composer.json of the specific package you are using to confirm.
- How do I publish the configuration files from this package?
- Run php artisan vendor:publish and select the vsymfo-core entry, or pass the tag or provider class registered in the service provider's publishes method. Published configuration lands in your config directory, where you can override the defaults per environment. Keep the published file under version control so environment differences stay visible.
- Which Laravel and PHP versions does mikoweb/vsymfo-core support?
- The supported versions are declared as constraints on illuminate/support and php in the package's composer.json. Run composer show mikoweb/vsymfo-core to see the exact requirements resolved for your project. Pin an appropriate constraint in your own composer.json before upgrading Laravel.
- Can I use mikoweb/vsymfo-core outside of Laravel?
- The package is built around Laravel service providers and configuration merging, so its most useful parts assume the framework's container and bootstrap process. Some plain PHP helpers and contracts may work standalone, but you would have to wire them yourself. For non-Laravel projects, lighter standalone libraries are usually a better fit.
- How do I test a package that depends on mikoweb/vsymfo-core?
- Add the package as a path or require-dev dependency and boot a minimal Laravel application in your test suite with Orchestra Testbench. Then assert that the service providers register and that configuration merges as expected. Keep provider and configuration assertions separate from your business logic tests so failures are easy to trace.
- Is mikoweb/vsymfo-core safe to use in production?
- Yes, it is a lightweight shared library rather than something that needs extra infrastructure or runtime services. Deploy with composer install --no-dev -o and cache your configuration and routes as usual. Because it publishes configuration, make sure production environment values are set before you cache config.
- What are the alternatives to mikoweb/vsymfo-core?
- For a single application, the closest alternative is writing the few providers and helpers you need directly in your app or a small internal package. The reason to adopt vsymfo-core is consistency across the VSymfo ecosystem rather than features you cannot get elsewhere. If you only need one or two utilities, a local trait or helper file may be simpler than adding a dependency.
- How is mikoweb/vsymfo-core maintained and how do I report issues?
- Use the GitHub repository for releases, issue reports, and pull requests, which is where bugs and feature requests are tracked. Because it underpins other VSymfo packages, changes may be coordinated across the ecosystem, so review the changelog before upgrading. Pin a version constraint in composer.json to avoid unexpected breaking changes in production.