Getting Started

This package appears to be a misnamed or misunderstood polyfill-cleanup utility—not an Unpoly integration. Despite its description claiming "Unpoly support", the repository name roxblnfk/unpoly, description ("Remove PHP-XX polyfill"), and score (0.365) suggest it’s either an abandoned experiment, a typo, or a non-functional placeholder. Do not use it for Unpoly integration. For actual Unpoly in Laravel:

Use the official unpoly/unpoly JS library via npm/yarn.
Integrate manually in Blade templates with <body data-unpoly-target> or use community packages like laravel-unpoly (if verified and maintained).
First check:
✅ Run composer show roxblnfk/unpoly --strict — if unknown, skip.
✅ Search Packagist/GitHub — if repo doesn’t exist or is private, do not install.

Implementation Patterns

If you do confirm this package is functional and intentional (unlikely):

Audit polyfills first: composer show -i | grep polyfill → verify what needs removal.

Add to deployment scripts only if safe:

# In `composer.json` scripts (post-autoload-dump, NOT post-update-cmd)  
"post-autoload-dump": ["@php vendor/bin/unpoly --only=php-7.4"]

Dry-run first: Confirm behavior with unpoly --dry-run (if implemented).
⚠️ Never run auto-removal in production without:
Full test suite pass
composer.lock committed
Manual rollback plan

Gotchas and Tips

Critical red flags:
- ⛔ Repository is unknown (not on Packagist/GitHub) → instability & security risk
- ⛔ Score (0.365) indicates no tests, no PSR, missing docs
- ⛔ "Unpoly" in name is misleading—this package has nothing to do with Unpoly JS
Operational risks:
- Removing polyfills without checking composer why symfony/polyfill-* may break dependencies (e.g., Laravel 10+ still uses some php80-* polyfills on PHP 7.4)
- unpoly may corrupt vendor/composer/installed.json or autoload_files.php if it manipulates Composer’s autoloader incorrectly
Safer alternatives:
- Upgrade PHP & dependencies (best)
- Use symfony/polyfill with version-specific packages only
- Manually remove via composer remove php-7.4-polyfill --no-update && composer update --with-all-dependencies
If forced to proceed:
1. Fork the package and audit code
2. Add to require-dev only
3. Run in CI before tests with unpoly --check && exit $? to fail fast
4. Keep composer.lock changes in PRs fully reviewed
💡 Rule of thumb: If the package doesn’t have 100+ stars, a GitHub repo, and clear usage docs, don’t use it—polyfill hygiene is too critical to gamble on unknown code.

Unpoly Laravel Package

Getting Started

Implementation Patterns

Gotchas and Tips