In our specific package case, we didn't need some features, but I do want to mention them and show you how to use them, in case your packages need them.
This one is pretty easy, you just create a Model class in the /src/Models of the package and namespace it correctly.
Then, your Controllers (or the Controllers outside the package) may just use the Model by loading it from the correct namespace....
For migrations, I would not overwrite the migration creation date What if someone runs the publish of your package, it creates a new migration file for them, and after running `php artisan migrate' it displays an error that such a table already exists
I use php artisan vendor:publish --all in composer.json
to update my packages after composer update, I often forgot about vendor:publish
{ ... "scripts": { "post-update-cmd": [ "@php artisan vendor:publish --all" ] }}A similar problem with creating a new migration again and again was e.g. in spatie/laravel-medialibrary
I created a PR that search a file by name without a date and they approved it
https://github.com/spatie/laravel-medialibrary/pull/3299/commits/96fd55782f8d0ada7360e139bf2e385f4750f925
It's very useful thank you very much