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

Dhosa Laravel Package

laravie/dhosa

Dhosa is a lightweight Laravel package from Laravie, built to drop into existing PHP apps with minimal setup. Install it via Composer and use its focused API to keep your codebase clean and maintainable while following standard Laravel conventions.

Deep Wiki
Context7

🔌 ‎ Hot Swapping for Laravel Eloquent

Frequently asked questions about Dhosa
What is laravie/dhosa used for?
Laravie Dhosa is a Laravel and Orchestra package that provides schema alteration helpers for database migrations. It works alongside Laravel's schema builder to make common column changes such as adding, changing, and dropping columns more concise and readable. It is intended for developers who want migration code to stay expressive without repeating boilerplate.
How do I install laravie/dhosa?
Install it through Composer using the package name laravie/dhosa. After installation, use its helpers inside your Laravel migration files where you would normally use the schema builder. Check the package metadata for service provider or configuration steps, since Orchestra applications may have different setup conventions.
Does laravie/dhosa work with Laravel migrations?
Yes. The package is described as supporting Laravel migrations and integrating with Laravel's schema builder. You can use its helpers for common schema alterations inside migration up and down methods. It is meant to complement, not replace, Laravel's migration system.
What kinds of schema alterations does Dhosa simplify?
Dhosa focuses on common schema alteration tasks, including adding columns, changing columns, and dropping columns. The goal is to keep these operations readable and maintainable in migration files. It is a lightweight helper layer rather than a full database abstraction.
Do I need to use Orchestra to use laravie/dhosa?
No, Orchestra is not required for typical Laravel usage. The package is built as a Database Helper for Orchestra Schema Alterations and supports Orchestra applications, but its overview also says it supports Laravel migrations. In a standard Laravel app, you can use it as a schema helper package.
How is laravie/dhosa different from Laravel's native schema builder?
Dhosa does not replace Laravel's schema builder. It adds focused helpers on top of it to make common column alterations more concise and expressive. That can reduce repetitive migration code while still following standard Laravel conventions.
Which Laravel versions are supported by laravie/dhosa?
The provided context does not list exact Laravel version constraints. You should check the package's composer.json or Packagist metadata before installing to confirm compatibility with your Laravel or Orchestra version. Composer will also enforce the declared framework constraints during installation.
Can I use Dhosa to rename or drop columns in migrations?
The package explicitly simplifies adding, changing, and dropping columns. Renaming columns is not mentioned in the provided overview, so verify that specific operation in the package documentation before relying on it. For supported changes, use the helpers within normal Laravel migration up and down methods.
Is laravie/dhosa safe to use in production migrations?
It is a lightweight helper for Laravel schema alterations, so production safety depends on the underlying database changes and your migration strategy. Test migrations in staging first, back up data, and review generated SQL for destructive operations such as dropping or changing columns. The package itself is described as following standard Laravel conventions.
How do I test migrations that use laravie/dhosa?
Run your normal Laravel migration tests against a test database, such as SQLite in memory or a dedicated testing connection. Because Dhosa integrates with Laravel's schema builder, the same migration and rollback tests you use for standard Laravel migrations should apply. Include assertions for the final schema after up and down migrations.
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.
robertmarney/lara-hierarchial-collections
simonschaufi/rule-doc-generator
emissaoja/emissaoja
blackbricksoftware/gravityforms-civicrm-form-processor
al-rahabi/fancy-crud
jinas/dhivatar-component
mltstephane/laravel-quality
bernskiold/laravel-talentlms
bernskioldmedia/laravel-form-architect
youbar/easy-crud
c-point-labs/laravel-hostyourai
dbravoan/dbcms-admin-theme-dbcms
dbravoan/dbcms-theme-db-cyber
dbravoan/dbcms-blocks-basic
dbravoan/dbcms-module-content-audit
dbravoan/dbcms-module-ai-assistant
paygate-to/paygate-php
padosoft/askmydocs-connector-base
defstudio/supercharged-carbon
bernskioldmedia/laravel-matomo