Babel plugin that rewrites property lookups, assignments, deletions, function invocations, 'in' statements, and 'for...in' loops to use function calls from a proxy-compat library, enabling Proxy semantics in environments like IE 11 that lack native Proxy support. Current stable version is 0.22.4, with maintenance-level releases. Key differentiator: allows using modern Proxy-based reactivity or interceptors while targeting legacy browsers without polyfilling Proxy itself. Typically paired with libraries like `proxy-compat` that provide the runtime helper functions.
npm install babel-plugin-transform-proxy-compatVerified import paths — ran on the pinned version, not inferred.
Configures Babel to transform Proxy operations to use proxy-compat runtime for IE 11 compatibility.
Use /* proxy-compat-disable */ comment at top of files that are performance-sensitive and do not use Proxy.
Update config to use { module: '...' } or { global: '...' } instead of just a string.Use resolveProxyCompat with module or global sub-option.
Ensure a global variable (e.g., window.MyProxyCompat) is defined via a script tag or other means.
Be aware that some property accesses may not be rewritten; test thoroughly.
Run: npm install proxy-compat --save
Change import to: import callKey from 'proxy-compat/callKey'; (not from 'proxy-compat')
Use: const ProxyCompat = require('proxy-compat'); (no .default)