Nova Redirects Laravel Package

Getting Started

Install the package with Composer, then publish its configuration if the package exposes one:

composer require <vendor>/<package>
php artisan vendor:publish --tag=<package-config>

Look first at the package’s config file and service provider registration. The 1.0.2 release specifically fixes a hardcoded status-code value, so the most important config key to inspect is the one controlling the HTTP status code returned by the package’s primary response path. Set that value explicitly rather than relying on the old hardcoded default.

A good first use case is the package’s simplest response-producing feature: configure the status code to something other than the previous hardcoded value, hit the relevant route or invoke the relevant class, and assert the response status with a feature test. That confirms the 1.0.2 fix is active in your application.

Implementation Patterns

• Drive status codes from configuration rather than scattering literals through controllers or middleware. The 1.0.2 fix makes this the intended pattern.
• If the package returns responses through a middleware, response macro, or dedicated responder class, wrap or extend that integration point so your application can override the status code per environment or per route.
• In tests, assert both the status code and response body. A regression test that sets a non-default status code in config is the fastest way to catch future hardcoding regressions.
• When integrating with Laravel’s HTTP layer, prefer returning the package’s response through the normal response pipeline so middleware, exception handling, and status-code assertions behave consistently.
• For multi-tenant or multi-context applications, resolve the status code at runtime from config or a context object rather than caching a single value at boot.

Gotchas and Tips

• The 1.0.2 change fixes a hardcoded status-code value. If you were previously working around that by overriding headers or patching responses, remove the workaround and use the config value directly.
• Run php artisan config:clear after upgrading if you use cached config. A stale cached config can make it look like the fix did not apply.
• Do not read the status code with env() directly in application code. Use config() so config caching and package defaults behave correctly.
• If the package exposes a config key for the status code, publish the config file and set the value explicitly. Relying on an unpublished package default makes upgrades harder to reason about.
• Check the package’s extension points—custom responders, macros, or container bindings—before subclassing internals. The status-code fix likely lives in one of those layers, and overriding the documented extension point is safer than monkey-patching.
• Add a regression test that sets the status code to a non-default value. This is especially important because hardcoded values can reappear in future refactors.