hardhat 2.11.0-dev.0 → 2.11.0

package/internal/util/antlr-prototype-pollution-workaround.d.ts

@@ -1,16 +0,0 @@
-/**
- * This function applies a workaround to an ANTLR issue that arises when used
- * with Immutable.js.
- *
- * ANTLR defines String.prototype.hashCode, and Immutable.js uses hashCode
- * functions internally (for equality), including on strings.
- *
- * If the parser is required lazily (which it normally is) in the middle of an
- * execution, the custom state managers can break, because we'd be redefining
- * the String's equality function as seen by Immutable.js.
- *
- * By always including the parser we make the equality function's definition
- * stable during the entire execution.
- */
-export declare function applyWorkaround(): void;
-//# sourceMappingURL=antlr-prototype-pollution-workaround.d.ts.map

package/internal/util/antlr-prototype-pollution-workaround.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"antlr-prototype-pollution-workaround.d.ts","sourceRoot":"","sources":["../../src/internal/util/antlr-prototype-pollution-workaround.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;GAaG;AACH,wBAAgB,eAAe,SAE9B"}

package/internal/util/antlr-prototype-pollution-workaround.js

@@ -1,22 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.applyWorkaround = void 0;
-/**
- * This function applies a workaround to an ANTLR issue that arises when used
- * with Immutable.js.
- *
- * ANTLR defines String.prototype.hashCode, and Immutable.js uses hashCode
- * functions internally (for equality), including on strings.
- *
- * If the parser is required lazily (which it normally is) in the middle of an
- * execution, the custom state managers can break, because we'd be redefining
- * the String's equality function as seen by Immutable.js.
- *
- * By always including the parser we make the equality function's definition
- * stable during the entire execution.
- */
-function applyWorkaround() {
-    require("@solidity-parser/parser");
-}
-exports.applyWorkaround = applyWorkaround;
-//# sourceMappingURL=antlr-prototype-pollution-workaround.js.map

package/internal/util/antlr-prototype-pollution-workaround.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"antlr-prototype-pollution-workaround.js","sourceRoot":"","sources":["../../src/internal/util/antlr-prototype-pollution-workaround.ts"],"names":[],"mappings":";;;AAAA;;;;;;;;;;;;;GAaG;AACH,SAAgB,eAAe;IAC7B,OAAO,CAAC,yBAAyB,CAAC,CAAC;AACrC,CAAC;AAFD,0CAEC"}

package/src/internal/util/antlr-prototype-pollution-workaround.ts

@@ -1,17 +0,0 @@
-/**
- * This function applies a workaround to an ANTLR issue that arises when used
- * with Immutable.js.
- *
- * ANTLR defines String.prototype.hashCode, and Immutable.js uses hashCode
- * functions internally (for equality), including on strings.
- *
- * If the parser is required lazily (which it normally is) in the middle of an
- * execution, the custom state managers can break, because we'd be redefining
- * the String's equality function as seen by Immutable.js.
- *
- * By always including the parser we make the equality function's definition
- * stable during the entire execution.
- */
-export function applyWorkaround() {
-  require("@solidity-parser/parser");
-}