fix: explicit module constraints (#672)

* fix(tsconfig): explicit module constraints These options are viral: enabling them in a package requires all downstream consumers to enable them as well. Consumers can now opt into these semantics, it also does not require them to do so. Consumers can always safely use alternative import syntaxes (including falling back to `require() `and i`mport()`), or can enable these flags and opt into this behavior themselves. * Create khaki-coats-cry.md --------- Co-authored-by: jxom <[email protected]>
wevm · Jun 11, 2023 · e033f46 · e033f46 · vercel · Jun 11, 2023
1 parent fe259a0
commit e033f46
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 0 deletions.
diff --git a/.changeset/khaki-coats-cry.md b/.changeset/khaki-coats-cry.md
@@ -0,0 +1,5 @@
+---
+"viem": patch
+---
+
+Turned off `esModuleInterop` & `allowSyntheticDefaultImports` in tsconfig.
diff --git a/tsconfig.base.json b/tsconfig.base.json
@@ -24,6 +24,8 @@
     "checkJs": false,
 
     // Interop constraints
+    "esModuleInterop": false,
+    "allowSyntheticDefaultImports": false,
     "forceConsistentCasingInFileNames": true,
     "verbatimModuleSyntax": true,