为何jQuery-migrate无法直接替换代码中的已弃用函数？

Great question—let’s break down the core reasons why jQuery Migrate works as a runtime shim instead of rewriting your or third-party code directly, and why that’s actually a good fit for your situation.

• It’s a runtime shim, not a static code transformer
  jQuery Migrate doesn’t read or modify your source files (including third-party library code). Instead, it runs alongside jQuery in the browser, and dynamically provides compatibility implementations when deprecated APIs are called. For example, if an old library calls $.browser, Migrate creates that property on the fly at runtime—there’s no need to edit the library’s code to add it back. This is very different from tools like Babel, which rewrite code during a build step.

• Third-party libraries are often minified/obfuscated, making static replacement risky
  Most unmaintained third-party libraries you’re using are probably minified (with variable names shortened and code compressed). Trying to do a simple string replace (like swapping $.live for $.on) would almost certainly break things—you might accidentally replace parts of variable names or unrelated code, leading to hard-to-debug errors. Migrate avoids this by targeting actual API calls at runtime, not static text in files.

• Deprecated APIs often need complex runtime logic, not just a rename
  Many old jQuery APIs don’t have a 1:1 replacement with new ones. For example, the old $.fn.toggle had two behaviors: toggling element visibility and toggling event handlers. The new $.fn.toggle only handles visibility. Migrate has to check the arguments passed to toggle at runtime to decide which old behavior to simulate—a static code replace couldn’t handle that context-dependent logic. Similarly, old $.ajax options might require translating to the new Promise-based structure, which needs runtime checks.

• It preserves the original library behavior without modification
  Even if you could safely replace a deprecated function name, you’d risk breaking the library’s internal logic. Many libraries rely on specific edge cases or return values of old jQuery APIs that aren’t identical to the new ones. Migrate’s shims are rigorously tested to replicate the exact behavior of deprecated APIs, so you don’t have to worry about introducing unintended bugs into unmaintained code.

In short, jQuery Migrate’s design is all about keeping your existing code (including third-party libraries) working without any changes—which is exactly what you need right now, since updating or modifying those unmaintained libraries isn’t feasible.

内容的提问来源于stack exchange，提问作者William