@lwc/engine-core 9.0.2 → 9.0.4-alpha.0

package/dist/framework/weak-multimap.d.ts

@@ -3,21 +3,11 @@
  * The goal is to avoid leaking the values, which is what would happen with a WeakMap<K, Set<V>>.
  *
  * Note that this is currently only intended to be used in dev/PRODDEBUG environments.
- * It leaks in legacy browsers, which may be undesired.
+ *
+ * This implementation relies on WeakRefs and FinalizationRegistry.
+ * For some background, see: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/WeakRef
  */
-export interface WeakMultiMap<T extends object, V extends object> {
-    get(key: T): ReadonlySet<V>;
-    add(key: T, vm: V): void;
-    delete(key: T): void;
-}
-declare class LegacyWeakMultiMap<K extends object, V extends object> implements WeakMultiMap<K, V> {
-    private _map;
-    private _getValues;
-    get(key: K): ReadonlySet<V>;
-    add(key: K, vm: V): void;
-    delete(key: K): void;
-}
-declare class ModernWeakMultiMap<K extends object, V extends object> implements WeakMultiMap<K, V> {
+export declare class WeakMultiMap<K extends object, V extends object> {
     private _map;
     private _registry;
     private _getWeakRefs;
@@ -25,6 +15,4 @@ declare class ModernWeakMultiMap<K extends object, V extends object> implements
     add(key: K, value: V): void;
     delete(key: K): void;
 }
-export declare const WeakMultiMap: typeof LegacyWeakMultiMap | typeof ModernWeakMultiMap;
-export {};
 //# sourceMappingURL=weak-multimap.d.ts.map