discord.js v14 migration blocked by lagging ecosystem plugins

Context

A discord.js v13 codebase is being migrated to v14, but several third‑party dependencies — command frameworks, voice wrappers, and utility libraries — have not yet published v14‑compatible releases. The core library upgrade succeeds, yet the bot cannot start because peer‑dependency resolution fails or runtime errors surface from the outdated plugins.

Constraint

The team must decide between two unsatisfactory paths: pin discord.js at v13 (with its shrinking support window and no security backports) and wait for the ecosystem to catch up, or proceed with the v14 migration while stubbing, forking, or replacing the lagging plugins. Both options carry maintenance risk and no documented guidance ranks one as preferable.

Question

What criteria should drive the decision to stay on v13 versus migrating core code and bridging plugin gaps when the ecosystem has not released compatible versions? Are there documented patterns for safely stubbing or forking lagging dependencies without introducing long‑term technical debt?