Weave Code
Polyfill Php83 Laravel Package
symfony/polyfill-php83
Symfony polyfill for PHP 8.3 backports PHP 8.3 features to older PHP versions, including json_validate, the Override attribute, mb_str_pad, str_increment/str_decrement, Date* exceptions, LDAP helpers, and stream_context_set_options.
symfony/polyfill-php83 brings PHP 8.3's new core features to older PHP versions, letting you use modern functions and classes without upgrading your runtime. It's part of the Symfony Polyfill family and requires no configuration—just install it via Composer and the missing features become available automatically.
json_validatefor fast JSON syntax checksOverrideattribute andmb_str_padfor multibyte paddingstr_increment/str_decrementfor alphanumeric strings- Date/time and SQLite3 exception classes for precise error handling
Frequently asked questions about Polyfill Php83
- What is symfony/polyfill-php83 used for?
- It backports PHP 8.3 core features to older PHP versions so libraries and applications can call them before upgrading. The polyfill covers json_validate, the Override attribute, mb_str_pad, str_increment and str_decrement, LDAP and stream context additions, plus new Date and SQLite3 exception classes. It is a drop-in Composer package under the MIT license. On PHP 8.3+ the native implementations are used instead.
- How do I install symfony/polyfill-php83 in Laravel?
- Run composer require symfony/polyfill-php83 or pin it as ^1.43 for the latest fixes. It is usually installed transitively by Symfony components already used in Laravel, so check composer show before adding it explicitly. No service provider or configuration is required. Commit the updated composer.json and composer.lock.
- Which PHP versions does symfony/polyfill-php83 support?
- It targets PHP versions below 8.3 and is commonly used on PHP 7.4 through 8.2, including Laravel 9 and 10 applications. On PHP 8.3 and newer the polyfill defers to native functions and classes. Laravel 8 on PHP 8.0 is partially compatible, so test the Override attribute and mb_str_pad. Laravel versions below 8 on PHP 7.4 should avoid the Override attribute.
- Is json_validate safe to use for Laravel API request validation?
- Yes, json_validate is the primary high-impact feature and recent polyfill releases fixed its edge cases, lowering correctness risk on API payloads. It checks whether a string contains valid JSON syntax before you decode it, which complements Illuminate Validation rules. It does not validate schema or required fields, so pair it with your existing validation layer. Prefer it for early rejection of malformed JSON bodies.
- Does symfony/polyfill-php83 work with Laravel 11?
- Laravel 11 requires PHP 8.2 or newer, so the polyfill remains useful on PHP 8.2 and is bypassed on PHP 8.3+. The package has no Laravel-specific integration and will not conflict with the framework. Composer will typically resolve it through Symfony dependencies. Test any code that relies on Override on PHP 8.2 to confirm expected behavior.
- Can I use the Override attribute on PHP 7.4 with this polyfill?
- The polyfill defines the Override attribute class so code using it can be parsed on older PHP versions, but attributes themselves require PHP 8.0 or newer to have any effect. On PHP 7.4 you should avoid the Override attribute entirely. On PHP 8.0 through 8.2 it works for IDE and static-analysis support. Use it to mark methods that intentionally override a parent method.
- Should symfony/polyfill-php83 be a dev dependency or production dependency?
- It should normally be a production dependency because the backported functions and classes must exist at runtime. In Laravel it is often already pulled in transitively by Symfony packages, so an explicit require is optional. Use require-dev only if the polyfill is needed solely by development tooling. Run composer update symfony/polyfill-php83 --with-dependencies when you need the latest patch release.
- Are str_increment and str_decrement reliable for version counters?
- The polyfill implements PHP 8.3 string increment and decrement semantics for alphanumeric strings, and recent releases fixed overflow and edge-case handling. They are suitable for versioning logic in models or services when you need human-readable counters. Test your specific input patterns, especially boundaries near PHP_INT_MAX or unusual characters. For simple integer counters, native integer increment remains simpler.
- Will symfony/polyfill-php83 conflict with other polyfills?
- Conflicts can occur if another library defines the same global functions or classes, so avoid mixing multiple polyfill packages that target PHP 8.3. It is designed for Symfony and Laravel stacks and is generally safe there. If you integrate with non-Symfony code such as WordPress plugins, verify function_exists guards and Composer resolution. Composer will usually prevent duplicate package installs but cannot prevent third-party function definitions.
- Is symfony/polyfill-php83 maintained and production ready?
- Yes, it is maintained by the Symfony project under the MIT license and is widely installed through Symfony components. Recent 1.43.x releases are purely corrective with no new symbols or signature changes, making them semver-safe. The main remaining edge cases are niche features like LDAP, ODBC quoting, and ini_parse_quantity, which matter only if your stack uses them. Pin ^1.43 and review patch releases for fixes.
Weaver
How can I help you explore Laravel packages today?