Weave Code
Core Bundle Laravel Package
snowcap/core-bundle
Snowcap Core Bundle provides a shared foundation for Laravel apps, bundling common services, helpers, and configuration defaults so teams can bootstrap projects faster and keep codebases consistent while cutting boilerplate.
Snowcap Core Bundle is a reusable Symfony bundle that collects the shared foundations used across Snowcap applications. It centralizes common configuration, service definitions, and small utilities, giving projects a consistent starting point while reducing duplicated boilerplate.
- Reusable Symfony services and sensible configuration defaults
- Shared Twig extensions and template helpers
- Common form types, event listeners, and Doctrine utilities
- Standard bundle extension for simple DI wiring
- Lightweight, modular components that can be adopted incrementally
Frequently asked questions about Core Bundle
- Is snowcap/core-bundle a Laravel package?
- No. Despite being reviewed alongside Laravel/PHP packages, snowcap/core-bundle is a Symfony bundle called SnowcapCoreBundle. It relies on Symfony bundle registration, DI container compilation, the event dispatcher, and kernel bootstrapping, which have no direct Laravel service-provider equivalent. For a Laravel-first stack, fit is effectively zero without a rewrite.
- Can I install snowcap/core-bundle in a Laravel application?
- Composer resolution will almost certainly fail before any code runs because its constraints target the Symfony 2.x era and PHP 5.5 to 5.6. Even if you force installation, there is no Laravel service provider, facade, or config publishing to integrate it. It is not a practical dependency for Laravel 9, 10, or 11.
- Which Laravel versions does snowcap/core-bundle support?
- None officially. The package predates modern Laravel and is built as a Symfony bundle rather than a Laravel package. It does not ship service providers, facades, package discovery, or publishable configuration. Do not expect support for Laravel 9, 10, 11, or newer.
- What Symfony and PHP versions does snowcap/core-bundle require?
- The last release was 2015-09-26, which places it in the Symfony 2.6 to 2.8 and PHP 5.5 to 5.6 window. Composer constraints may not even be declared clearly, so assume old requirements until proven otherwise. It will not coexist cleanly with PHP 8.x or Symfony 5, 6, or 7.
- What is actually inside snowcap/core-bundle?
- The naming suggests an internal grab-bag of shared services, base classes, form types, Twig extensions, or admin scaffolding used across Snowcap projects. That is the least portable shape a package can take because it may hide coupling to private packages. Audit the source before assuming any component is reusable.
- Is snowcap/core-bundle maintained or abandoned?
- It is effectively abandoned. The last release was in 2015, there is no evidence of CI or test coverage, and it has only 3 stars and 0 dependents. There is no ecosystem signal or community watching it, so adoption means instant fork tax with zero upstream support.
- Is snowcap/core-bundle safe for production use?
- Technical risk is high and concentrated in abandonment. If the bundle includes routing, form handling, uploads, or admin controllers, those are exactly the areas where ten-year-old code becomes a security liability. Confirm the license before lifting any code, and treat the repository as a reference implementation rather than a production dependency.
- How do I migrate from snowcap/core-bundle to Laravel?
- Do not port the whole bundle. Audit it for useful patterns, then reimplement the valuable 20 percent natively as a Laravel package with service providers, facades, and config publishing. Re-test anything ported against current PHP with strict types and deprecation warnings enabled.
- What are alternatives to snowcap/core-bundle for shared Laravel utilities?
- For Laravel, use maintained Laravel packages or build an internal Composer package with service providers, package discovery, and publishable configuration. For legacy Symfony 2.x applications, prefer maintained Symfony bundles that match your framework version. Avoid dormant 2015-era code when a small native package can cover the same shared utilities.
- Can I fork snowcap/core-bundle and use it in a modern project?
- Only conditionally. Confirm the license is permissive, fork the repository, drop or loosen version constraints, run static analysis, strip unused code, and vendor it under an internal namespace rather than publishing it as a public Composer dependency. Assume PHP 5.6 to 7.0 and Symfony 2.x until proven otherwise, and re-test everything against current PHP.
Weaver
How can I help you explore Laravel packages today?