Weave Code
Contracts Laravel Package
sebwite/contracts
Sebwite Contracts provides a lightweight contract layer for Laravel and PHP projects, helping define clear interfaces between components. It improves type safety, keeps integrations explicit, and makes code easier to test, extend, and maintain.
A theme framwork for your next web application. Theme inheritence, powered by Laravel and Assetic, can be used in any application!
Frequently asked questions about Contracts
- What is sebwite/contracts used for in Laravel?
- Sebwite Contracts is presented as a Laravel theme framework with theme inheritance and Assetic-powered asset handling. Its blurb also describes a lightweight contract layer for defining interfaces, so confirm the actual API before adoption. In practice, treat it as legacy theme and asset code, not a modern Laravel package.
- Does sebwite/contracts support Laravel 10 or Laravel 11?
- No supported Laravel version range is evident from the available metadata. The package appears tied to older Laravel and Assetic assumptions, so Laravel 10 or 11 support should not be assumed. Validate Composer constraints and run a disposable-app spike before planning adoption.
- How do I install sebwite/contracts with Composer?
- It is a Composer package named sebwite/contracts, but Packagist availability and repository access must be confirmed first. If resolvable, require it in a legacy Laravel application and pin a specific commit or fork. Do not use a floating constraint for production.
- Is sebwite/contracts compatible with PHP 8?
- PHP 8 compatibility is unproven and likely risky because Assetic and legacy Laravel dependencies may be abandoned or incompatible. Check dependency constraints, run static analysis, and smoke-test theme resolution and asset builds on your target PHP version. Expect deprecation warnings or fatal errors until proven otherwise.
- Does sebwite/contracts require Assetic?
- The overview says it is powered by Laravel and Assetic, so Assetic is likely part of the theme and asset workflow. Determine whether it is required at build time, runtime, or both, and whether the contracts can be used without it. Isolate any Assetic coupling behind application-owned adapters.
- How does theme inheritance work in sebwite/contracts?
- Theme inheritance is a stated feature, but fallback order, cache behavior, and asset URL resolution are undocumented in the provided context. You must prove parent and child theme resolution, cache invalidation, and missing-theme fallbacks in a spike. Wrap resolution behind your own interfaces so it remains replaceable.
- Is sebwite/contracts actively maintained?
- There are no meaningful maintenance signals: zero stars, zero dependents, and a Bitbucket-hosted repository. Treat it as internally owned custom code rather than a supported third-party product. Plan for forking, pinning, patching, and eventual replacement.
- Can I use sebwite/contracts with Vite instead of Assetic?
- Vite is not a natural fit because the package is described around Assetic and legacy server-side theme resolution. You could use it only behind an adapter that generates asset URLs, but that adds risk and complexity. For modern Laravel, prefer Blade view namespaces or a custom theme resolver with Vite.
- What are alternatives to sebwite/contracts for Laravel themes?
- For modern Laravel, use Blade partials, view namespaces, and Vite, or a maintained theme package that explicitly supports your Laravel version. If you need inheritance, build a small application-owned theme resolver with clear fallback and cache rules. Avoid adopting an unmaintained Assetic-based package for new work.
- How should I test sebwite/contracts before using it in production?
- Timebox a disposable Laravel app and test Composer resolution, service-provider registration, theme inheritance, fallback themes, asset compilation, cache clears, and rollback. Run static analysis and a PHP and Laravel compatibility matrix, and confirm license and repository access. If viable, fork, pin, add tests, and feature-flag one low-risk theme.
Weaver
How can I help you explore Laravel packages today?