Because Maravel-Framework is a DI centered framework, the efficiency of its container is crucial.

Version 10.64 introduces FormRequest in Maravel Micro-Framework 10.52.25.

Version 10.64 of Maravel-Framework removed the \Illuminate\Foundation\Providers\FormRequestServiceProvider, leading to faster registration and boot times.

Please note that using $app->resolving or $app->afterResolving events, the speed of the container decreases because for each resolve, all events are looped to search via === or instanceof for the ones that need to be triggered.

• 10.8k dev commands

• 10.2k test classes

• 3.7k remaining test classes in v10.63.5

The tests using these MOVED classes must be updated with \MacropaySolutions\MaravelFrameworkDev\ instead of Illuminate\ FQN prefix.

The old tests will fail for sure because of this but production code should not if it does not use fake/test code/classes.

Versions 2.0.0 of laravel-crud-wizard-decorator-free and version 7.1.0 of laravel-crud-wizard-free introduce an important response time improvement by eliminating useless json_decode and json_encode calls between the controller and the middlewares.

Because the controller resolves the JsonResponse from DI, the CrudProvider registers a binding for it in which the json_encode is skipped when the data needs decoration.

This follows Maravel-Framework s design of DI first logic and it works also in Laravel and Lumen.

Because I dislike runtime reflection, I improved the autowiring:cache command to include also constructors, not just methods.

If the concrete has contextual bindings (and constructor parameters) the old reflection is still used.

If the parameters are sent as array list, concrete will be instantiated directly with them. On failure, it will default to the old reflection but at the cost of building an Exception.

The official web page https://maravel-framework.com/docs/ now holds links to the official updated documentation of the Maravel-Framework s Templates.

• Maravel Micro-Framework Docs

• Maravelith Docs

• Maravel-Framework Wiki

The docs were updated, starting from Lumen and Laravel 10 docs, with the fixes and improvements up to Maravel-Framework 10.62.8.

Last night at 8:50 PM, I sat down to rebuild a product's backend from scratch. By 11 PM, I had a complete Laravel API with auth, CRUD, real-time WebSockets, and chat. By 1:50 AM, the existing React Native frontend was wired up and running against it locally. Deployed to the cloud the next morning.

That's about two hours for the entire backend. Five hours total including frontend integration.

Here's how multi-agent orchestration, Laravel, and solid documentation made that possible.

What I Was Building

Version 10.55.0 lost ~10.8 k rows of dev environment code that was moved to a separate package. https://marius-ciclistu.medium.c...

Version 10.56.0 brings faster boot time for apps that have many listeners for events and/or observers by improving the way they are registered, including caching the observers when events are cached. https://marius-ciclistu.medium.c...

Maravel-Framework 10.54.3, which is used in Maravel Micro-Framework and Maravelith Template, restricts the devCommands to local environment and by doing this, it speeds up the boot of the application. Also it contains a back-port for \Illuminate\Console\Prohibitable with the mention that these classes are by default prohibited from running in production:

• \Illuminate\Database\Console\Migrations\FreshCommand

• \Illuminate\Database\Console\Migrations\MigrateMakeCommand

• \Illuminate\Database\Console\WipeCommand

• \Illuminate\Database\Console\Migrations\ResetCommand

• \Illuminate\Database\Console\Migrations\RefreshCommand

• \Illuminate\Database\Console\Seeds\SeedCommand

The differences to Laravel/Lumen are:

Maravel 10.51.4 can process woth 15.965% more requests per second vs Lumen 10. This is without caching for config or routes and without opcache preload. More details https://github.com/myaaghubi/PHP...

Version 5.1.0 of laravel-crud-wizard-free will include a backward compatible (laravel >= 8) major performance improvement for reducing the number of set calls during updates when using casts. Also a new feature of locking the model to prevent updates will come as a bonus. Maravel-Framework 10.53.2 will also contain this improvement at a larger scale than the one possible via an external package. It will support prevention of updates also. More details .

Most people think users choose products based on features or price. In reality, support decides who stays.

A cheaper tool becomes expensive fast when every issue turns into a ticket nightmare. Meanwhile, teams keep paying more for products that solve problems and support them when it matters.

Support is not a cost. It is part of the product experience. Fast replies build trust. Clear answers reduce churn. Companies that treat support as a growth lever win.

I really wonder these questions

Most people think users choose products based on features or price. In reality, support decides who stays.

A cheaper tool becomes expensive fast when every issue turns into a ticket nightmare. Meanwhile, teams keep paying more for products that solve problems and support them when it matters.

Support is not a cost. It is part of the product experience. Fast replies build trust. Clear answers reduce churn. Companies that treat support as a growth lever win.

I really wonder these questions

Built for who needs more than Laravel can/wants to offer in terms of APIs.

This includes both new features and retroactive bug fixes.

If things like:

• auto incrementing via API

• auto filtering via API

• auto aggregating via API on the resource's & relations' columns

• auto streamed JSON Lines response

• auto CSV streamed download

• auto XLS download with relations in separate sheet (for current page)

• auto MVCC DB "select count(*) from table" slow query solution in MySql >= 8

• auto prevent DB blocking via API with long running queries for mysql >= 5.7.4 and mariaDB >= 10.1.1

• auto composite primary key handling

• read-only DTO for model

• auto update the one to one relations on resource update

• retroactive vulnerability fix for eager loading relations in global scopes

• and many more features that you can read about here: https://github.com/macropay-solu...

  seem unbelievable at first glance, be my guest and see for your self: https://laravel-crud-wizard.com