Getting Started

Treat 2.0.0-alpha3 as pre-release: pin the exact version in composer.json and avoid using it as a production dependency without a rollback plan.
The release note only points to the hubleto/erp repository, so start there: review its README, installation docs, migrations, and example modules before touching your Laravel app.
Minimal path: install via Composer, publish any package config/assets, run migrations, and register the package service provider if it is not auto-discovered.
First practical use case: scaffold a small ERP-adjacent module or read-only dashboard against the package’s models/controllers, rather than attempting a full ERP replacement on day one.

Implementation Patterns

Follow the package’s module structure: keep customizations in your own service provider/module namespace and extend package classes rather than editing vendor code.
Use Laravel’s container and config publishing to override package services, routes, and views; avoid hard-coding assumptions about internal class names in alpha code.
Integrate through the package’s public models/controllers first, then add custom workflows as separate classes that depend on stable interfaces.
For day-to-day work, create a thin adapter layer in your app (repositories or actions) around package APIs so alpha-level changes stay contained.
Use feature tests around any ERP data mutations; alpha packages often lack comprehensive test coverage, so your own regression tests become the safety net.

The release note is effectively uninformative: “See hubleto/erp repository for more details.” Check that repo’s changelog, issues, and commit history before upgrading.
Alpha versioning means breaking changes can arrive without deprecation cycles. Pin versions and review diffs between alpha tags.
Expect sparse documentation for edge cases; debugging often means reading source and the main hubleto/erp repository rather than package docs.
Config quirks are likely around module registration, route prefixes, and asset publishing. Publish config early and keep it under version control.
Extension points to watch: service provider bindings, module registration arrays, model/controller base classes, and migration hooks. Prefer these over monkey-patching vendor files.
If the package relies on the broader Hubleto ERP codebase, verify compatibility between the package version and the hubleto/erp version before deployment.