Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
View Bundle

View Bundle Laravel Package

imatic/view-bundle

IMatic View Bundle offers a simple, flexible view layer for PHP apps, with reusable templates, helpers, and a clean API for passing data to views. It helps organize presentation logic and integrate rendering into existing projects while keeping templates maintainable.

View on GitHub
Deep Wiki
Context7

Bundle with predefined UI components

Frequently asked questions about View Bundle
What is Imatic View Bundle used for?
Imatic View Bundle is a lightweight PHP package for organizing and rendering application views through a reusable API. It helps separate layouts, partials, and view logic so templates stay modular and presentation code stays out of application logic. It is aimed at Laravel and other PHP projects that need a simple view layer with minimal setup.
How do I install Imatic View Bundle in a Laravel project?
Install it with Composer using composer require imatic/view-bundle. Then follow the repository README for any framework registration or configuration steps needed in your Laravel or PHP app. Because setup is described as minimal, you should be able to wire it into an existing project without restructuring your templates.
Does Imatic View Bundle support Laravel 10, 11, or 12?
The provided context does not list specific Laravel version constraints, so check the package composer.json and README before adopting it. Laravel compatibility depends on the package's PHP and illuminate/support requirements. Test the package against your target Laravel version in a branch or staging app first.
How do I configure view paths in Imatic View Bundle?
Imatic View Bundle supports configurable view paths so you can point rendering at the template directories your project uses. The exact configuration keys and file format should be confirmed in the repository README or config files. Keeping layouts and partials in dedicated paths makes the setup easier to maintain.
Can I use layouts and partials with Imatic View Bundle?
Yes, layouts and partials are core features for reusing view fragments and keeping templates modular. You can define shared layout templates and include partials for repeated UI pieces. The package's API is designed to keep that rendering logic clean and reusable.
How do I pass data to views with Imatic View Bundle?
The package provides a clean API for passing data into views, consistent with its goal of separating presentation from application logic. Check the README for the exact method names and data array format. In practice you would build a data array in your controller or handler and hand it to the view renderer.
Is Imatic View Bundle a replacement for Laravel Blade?
No, Imatic View Bundle is a lightweight view layer, not a full Blade replacement. Blade offers Laravel-specific directives, components, and ecosystem integration that this package does not claim to replicate. Use it when you want a simple, reusable rendering API, and keep Blade if you depend on its advanced features.
Can I use Imatic View Bundle outside Laravel in plain PHP?
Yes, it is described as a PHP package for Laravel and PHP projects, with framework-friendly integration and minimal setup. You can use it in plain PHP applications as long as your PHP version and autoloading meet the package requirements. Confirm the exact requirements in composer.json before installing.
How do I test views rendered with Imatic View Bundle?
Test rendered output by asserting the final view string or response rather than testing template internals. Point the package at fixture view paths so tests are isolated from application templates. Use your normal PHPUnit or Pest setup and include cases for missing templates, data passing, and layout composition.
Is Imatic View Bundle actively maintained and safe for production?
Before using it in production, review the GitHub repository for recent commits, releases, open issues, and tagged versions. Pin a specific Composer version and run the package through your staging environment. Because the provided context does not include a maintenance policy, treat release activity as your signal for long-term support.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console
pnscripts/filament-broadquill-lite
pnscripts/laravel-sentfold-lite
vleap/mx-sdk-laravel-internal
twidpay/utils
htetmyathlaing/scout-elasticsearch-driver
artisan-toolbox/front-awesome
ls/client-assistant
users-au/laravel-client
cgv/localized-resource