Weave Code
Core Laravel Package
jtc-solutions/core
A foundational Laravel package that bundles shared service providers, configuration defaults, helpers, and reusable building blocks for JTC Solutions applications, keeping common logic consistent and cutting boilerplate across projects.
Core bundle for every application in JTC that follows standard processes.
Frequently asked questions about Core
- Is jtc-solutions/core compatible with Laravel?
- The package overview says it is a Laravel foundation, but the v1.1.1 release notes show Symfony HttpKernel and Translation component idioms, including a kernel.exception ExceptionListener and %key% translation parameters. There is no Laravel service provider, no extra.laravel auto-discovery block, and no config publishing. A Laravel integration would require porting the exception listener to Laravel's Handler pipeline and rewriting translation parameter conventions.
- How do I install jtc-solutions/core with Composer?
- Installation is standard via composer require jtc-solutions/core. However, Laravel package discovery will not register it because the release evidence shows no extra.laravel block or Laravel service provider. Do not assume it will boot in a Laravel app without manual wiring or a port.
- Does jtc-solutions/core support Laravel package discovery?
- The overview claims auto-registration through Laravel package discovery, but the v1.1.1 release notes show no extra.laravel auto-discovery surface. Two consecutive releases have zero Laravel-facing integration. Treat the discovery claim as unverified or inaccurate until a Laravel service provider and discovery metadata appear.
- What Laravel versions does jtc-solutions/core support?
- No Laravel version constraint or Laravel integration is shown in the release evidence. The package references Symfony HttpKernel and Translation components instead. There is no declared Laravel support to evaluate against Laravel 9, 10, 11, or later.
- Can I publish configuration for jtc-solutions/core in Laravel?
- No config publishing tags, mergeConfigFrom calls, or publishable Laravel config assets are shown in the release notes. The package describes shared configuration helpers, but not Laravel-native config publishing. You would need to verify or build that layer yourself.
- What does the ExceptionListener in jtc-solutions/core do?
- It is a Symfony kernel.exception listener that forwards translation parameters to a translator. It also auto-wraps parameter keys in % delimiters, which is Symfony translator syntax. Laravel has no equivalent construct because its exception handling runs through Handler render and report methods, and its translator uses :key placeholders.
- Is jtc-solutions/core safe for production Laravel apps?
- The technical risk is high. The package has zero stars, zero dependents, one publisher, and roughly nine pull requests total, so there is no downstream validation. The v1.1.1 patch includes a vague upgraded notifications item and a translation delimiter behavior change, both of which could affect behavior without a Laravel integration path.
- How active is jtc-solutions/core maintenance?
- Activity appears low. After at least two tagged releases, the project has processed roughly nine pull requests total, with one publisher and no visible community. The changelog is auto-generated with a duplicated Full Changelog line, suggesting limited release-note proofreading. Treat bus factor as one and validate the tracker directly.
- Are there Laravel alternatives to jtc-solutions/core?
- For Laravel, the native foundation is Laravel's own service provider lifecycle, config repository, container bindings, and package discovery. Shared package helpers can be built with Laravel-native conventions rather than Symfony kernel and translator idioms. This package does not provide a Laravel-native replacement for those pieces.
- What changed in jtc-solutions/core v1.1.1?
- The release includes bug fixes, a vague upgraded notifications item shipped on a patch bump, and a translation parameter change that auto-wraps keys in % delimiters. It also adds or adjusts an ExceptionListener that forwards translation parameters. Nothing in the release adds Laravel service providers, discovery, config publishing, facades, or typed bindings.
Weaver
How can I help you explore Laravel packages today?