chore(deps): update dependency typechain to v8

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
typechain	^5.1.2 -> ^8.0.0

---

Release Notes

ethereum-ts/Typechain

v8.1.1

Compare Source

Patch Changes

• bbc9656: Skip run if project has no ABIs

v8.1.0

Compare Source

Minor Changes

• 63691c4: - Expose TypechainUserConfig type.
  • Removed contractName from interface output see #​692 for details.

v8.0.0

Compare Source

Major Changes

• 3a8a99a: Directory tree in generated types now reflects the directory tree in the inputs. Also, only the main contract
  type is reexported from each file.

  This change solves a number of name clashing problems. All generated code can still be imported after updating the
  import path.

• 978490f: We are not emitting contractName fields on contracts and factories anymore.

  Why?
  contractName breaks polymorphism for example: exact token implementation is not assignable to token interface.

  What do to?
  We are adding optional flag --discriminate-types to continue emitting contractName.

• 975a9dc: Fix type generation for arrays of nested structs ex: GovernanceMessage.Call[][] calldata _remoteCalls.

  Fix structs parser in typechain package. Now only struct tuples are registered.

Minor Changes

• 5b9a7fb: typechain will now resolve targets better in cases where the core package is symlinked
• e447bfb: Added optional config.inputDir property and --input-dir flag to control directory structure in generated
  types. If not set, it's inferred as lowest common path of all ABI files.
• a59ae6e: Prefer import type in generated files when possible

Patch Changes

• e1f832c: Make parsing JSON abi files more resilent. This should improve foundry integration.

v7.0.1

Compare Source

Patch Changes

• 7e7bbed: Add support for foundry / forge style artifacts

v7.0.0

Compare Source

Major Changes

• 92939ea: Structs will be namespaced using contract name when available

Patch Changes

• d244e41: Fix event name generation for events with arrays

v6.1.0

Compare Source

Minor Changes

• 63691c4: - Expose TypechainUserConfig type.
  • Removed contractName from interface output see #​692 for details.

Patch Changes

• de656c6: Add dontOverrideCompile setting
• Updated dependencies [63691c4]
• Updated dependencies [015abb2]
  • [email protected]
  • @​typechain/ethers-v5@​10.1.0

v6.0.5

Compare Source

Patch Changes

• 135f6ce: Fix structName for nested array of struct

v6.0.4

Compare Source

Patch Changes

• a26ea50: Constant size struct arrays are now properly supported and don't cause malformed TS emit anymore.

v6.0.3

Compare Source

Patch Changes

• a0fba00: Ethers V5 target doesn't emit unused imports anymore.

v6.0.2

Compare Source

Patch Changes

• ffc67f2: Fix "unused type parameter" ts error

v6.0.1

Compare Source

Patch Changes

• 44a04c0: Fix bug in parsing names of free floating structs

v6.0.0

Compare Source

Major Changes

• cd73777: Improve typings for events. Generate types for queryFilter for events.

  Note: This is a breaking change as it requires using TypeScript >= 4.0.0 (previously 3.9 was fine.)

  Example:

  const filter = contract.filters.Transfer() // TypedEventFilter<>
  const result = await contract.queryFilter(filter) // TypedEvent<>
  
  result[0].args.from // type support for named event parameters
  result[0].args[0] // type support by index
  
  contract.on(filter, (from, to, value, event) => {
    from // string
    to // string
    value // BigNumber
    event // TypedEvent<>
  })

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 8.x releases. But if you manually upgrade to 8.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.