Releases, and the engineering behind them. Mostly the bugs, because that is where the interesting part is.
Nova took $resourceKey in its controllers and declared {resource} in its routes, so the container could not resolve the parameter and every one of its routes raised an error instead of rendering. It also claimed /admin, which is how it was finally noticed.
The packageloadMigrationsFrom() was guarded by a check for a binding nothing ever created, so it silently did nothing. Every package following the documented API shipped a migration that could never run. Found by building one.
The packageThe starter kit shipped no .htaccess, so a deployed application answered the home page and returned 404 for everything else. Three development environments each hid it for a different reason, and the one that shows it is the one you only reach after deploying.
The packageWe use cookies
We use essential cookies to make our site work. With your consent, we also use analytics cookies to improve it.