Weave Code
Core Laravel Package
devanoxltd/core
Core package for Laravel projects by Devanox, providing module support, helpers, and multi-tenancy features. It includes publishable config, migrations, views, translations, and assets, plus tenancy setup commands. Built for Devanox Private Limited projects on Laravel 13 and PHP 8.5+.
Devanox Core is a Laravel package providing reusable foundations for Devanox projects, including module support, global helpers, and multi-tenancy capabilities. It ships publishable configuration, migrations, views, translations, and assets for easy integration into new or existing applications.
- Modular architecture for organizing application features
- Multi-tenancy setup with dedicated configuration and migrations
- Global helpers for common Laravel tasks
- Publishable resources for config, views, translations, and assets
- Designed for PHP 8.5+ and Laravel 13.x
Frequently asked questions about Core
- How do I install devanoxltd/core in a Laravel application?
- Install it with Composer using composer require devanoxltd/core. After that you can publish all bundled resources at once with php artisan vendor:publish --tag="core", or publish individual resources using the per-resource tags. The package requires PHP 8.5 or higher and Laravel 13.x, so confirm your environment meets those constraints before installing.
- What PHP and Laravel versions does devanoxltd/core require?
- The README states PHP 8.5 or higher and Laravel 13.x. That is a very narrow, forward-looking support window, so it will not install on current PHP 8.2/8.3 or Laravel 10/11/12 applications. Check the require block in composer.json on Packagist before adding it to an existing project.
- How do I publish the config, migrations, views, translations and assets?
- Run php artisan vendor:publish --tag="core" to publish everything at once, or use the granular tags: core-config, core-migrations, core-views, core-lang and core-assets. Migrations are published with core-migrations and then applied with php artisan migrate. Published files land in your app's config, database/migrations, resources/views, lang/vendor and public directories and can be edited freely.
- How do I set up multi-tenancy with devanoxltd/core?
- The package includes a tenancy installation command alongside tenancy-specific configuration and migrations. Publish the tenancy config and migration files first, then run the tenancy install command documented in the README. Because the tenancy documentation is still thin, plan time to read the published config file and migration schema before wiring it into a production tenant flow.
- Why aren't the package translations showing up in my Laravel app?
- This package ships its language files under the eng locale rather than en. If your application's default locale is en, set APP_FALLBACK_LOCALE=eng in your .env file so the package strings resolve. Alternatively, publish the files with the core-lang tag and create an en copy under lang/vendor/core to override individual strings.
- Does devanoxltd/core provide module support like nwidart/laravel-modules?
- It advertises module support as one of its three core features, alongside helpers and multi-tenancy. Unlike nwidart/laravel-modules, there is no public authoring guide, API reference or migration path documented, so the module system's behaviour and conventions must be reverse-engineered from the source. If modularity is your primary requirement, compare it against nwidart/laravel-modules and Laravel's native package discovery before committing.
- Can I disable or bypass the license verification in devanoxltd/core?
- There is no documented switch, offline mode or grace period for the license verification subsystem. Because the package bundles modules, helpers and licensing into a single dependency, you cannot adopt the module system without also adopting the license check. If you need the other features without the phone-home, get written confirmation from Devanox that the license layer can be disabled, or plan to fork the package.
- What license is devanoxltd/core released under and can I use it commercially?
- The licensing position is ambiguous: the repository reports NOASSERTION, prior analysis references GPL-3.0, and the package is described as internal to Devanox Private Limited projects. Those are mutually incompatible stances, and GPL-3.0 in particular has strong copyleft implications for closed-source products. Have legal confirm the actual grant in writing before shipping it in anything you distribute commercially.
- Is devanoxltd/core tested and safe to run in production?
- The README surfaces a GitHub Actions tests badge, but the repository has zero stars and zero dependents and the public documentation covers only installation. There is no module authoring guide, helper reference or license-key lifecycle documentation, so verification is manual rather than repeatable. Treat it as a vendor dependency: pin the version, review the source, and add integration tests around any licensing or tenancy behaviour you depend on.
- Is devanoxltd/core actively maintained and what are the alternatives?
- It is an internal Devanox package published for external consumption, so roadmap control and support commitment rest with a single vendor rather than an open-source community. For the individual concerns, evaluate nwidart/laravel-modules or native Laravel package discovery for modularity, stancl/tenancy for multi-tenancy, and an internal Composer package for helpers. Adopt devanoxltd/core only if you specifically need the bundled Devanox stack and have accepted the license and continuity risks.
Weaver
How can I help you explore Laravel packages today?