Missing migration guide for a widely used PHP polyfill
Problem
A temporary PHP fix released in 2014 has been downloaded about 20 million times, but the maintainer now wants to deprecate it. However, there is no official migration guide or deprecation notice, causing confusion for users upgrading, as older versions remain visible in public resources and may mislead future developers.
Pain points
- Lack of official migration guide and deprecation notice
- Old versions remain visible in public communities (e.g., Stack Overflow) leading to confusion
- Users lack a clear path to safely replace the polyfill
Questions to verify
- Have you used this polyfill in your project?
- Do you need official migration documentation or example code?
- Would you be willing to contribute resources or feedback for the migration?
Evidence
quote · @匿名
There is nothing as permanent as a temporary fix that works.
fact
My temporary PHP fix from 2014 has nearly 20M installs. Today I'm deprecating it
quote · @匿名
For a package with that kind of install base, is there a final release that prints the migration options in a deprecation notice? People will find it years from now through old Stack Overflow answers.
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.