new packages not compiling

[Morgosh]

Which compiler are you using?

• zksolc
• zkvyper

Which version of Solidity or Vyper?

0.8.13

zksolc/zkvyper version?

latest

Explain the issue

Hello guys, last couple days there were many package updates on zksync, though while I understand you are still working on it, but compiling contracts just doesn't work whatever I try, for me and many other developers, I would appreciate if some solution is presented in dev-general in discord on which packages to use for it to work.

    "@matterlabs/hardhat-zksync-deploy": "^1.1.0",
    "@matterlabs/hardhat-zksync-solc": "^1.0.3",
    "@matterlabs/hardhat-zksync-verify": "^1.2.0",
    "ethers": "^6.9.0",
    "zksync-ethers": "^6.0.0"

TypeError: Class extends value undefined is not a constructor or null

Link to your repo?

No response

[SebaBau]

Yeah, like @Morgosh wrote I have a lot of problems right now for example with upgradeable contracts (looks like problem with zksync-ethers).

[MexicanAce]

Hey @Morgosh , thank you for the report! We're investigating and will post updates here

[NOOMA-42]

Hey @MexicanAce any update on this? I still encounter same issue

update:
In my case, after installing "@nomicfoundation/hardhat-verify": "^2.0.3", the error, TypeError: Class extends value undefined is not a constructor or null magically solve, but the cause is still unclear to me. maybe zksync team could investigate further.

[mpopovac-txfusion]

Hey @Morgosh, I tried to replicate the error, and I didn't succeed. From the dependencies mentioned in the issue, the only one missing is hardhat. When I added that, it successfully compiled the contracts and deployed them. The only thing that crosses my mind here is that there might be an issue with dependencies. The error stated here, TypeError: Class extends value undefined is not a constructor or null, arises when you have installed zksync-ethers but haven't installed the ethers dependency.
Could you please provide the repository link? Or at least the hardhat.config file and package.json?

[Morgosh]

I excluded the contract/hardhat part from my project and was able to get it to work, was using yarn monorepo, so I can't really figure out which package was conflicting. But can confirm that I got it working by having latest packages and making sure there are no conflicting ones:

"@matterlabs/hardhat-zksync-deploy": "^1.1.0",
"@matterlabs/hardhat-zksync-solc": "^1.0.3",
"@matterlabs/hardhat-zksync-verify": "^1.2.0",
"@matterlabs/zksync-contracts": "^0.6.1",
"ethers": "^6.9.0",
"hardhat": "^2.19.2",
"zksync-ethers": "^6.0.0",

by running:

yarn add -D hardhat @matterlabs/hardhat-zksync-deploy @matterlabs/hardhat-zksync-solc @matterlabs/hardhat-zksync-verify @matterlabs/zksync-contracts ethers zksync-ethers

Also make sure to uninstall zksync-web3

[SebaBau]

But still there are some errors for example with tests. Errors occurs when "zksync-ethers" is installed. Also still is the problem with upgradeable contracts...

[mpopovac-txfusion]

Hey, this is probably connected to the way you are using it because there are some changes in the interface between ethers v5 and ethers v6. I would strongly recommend going through the migration guide (https://docs.ethers.org/v6/migrating/, https://era.zksync.io/docs/api/js/zksync2-js/migration.html).

The PR for the docs with updated examples is merged, but the documentation is yet to be released. Nonetheless, here is the PR link so you can check it out and see if this can resolve your issues: https://github.com/matter-labs/zksync-web-era-docs/pull/823/files

[Morgosh]

zkSync documentation is yet to be updated, I had the same issue with tests, where I got
Cannot read properties of undefined (reading 'url')

But found a temporal solution by adding the following to config:
"http://localhost:8545": {
url: "http://localhost:3050",
ethNetwork: "http://localhost:8545",
zksync: true,
}

naming is important since the new deployer seems to always read from this config name "http://localhost:8545"

[SebaBau]

Yeap, that solution works :)

[SebaBau]

Thank you for the answer, @Morgosh helped me a lot, looks like this "workaround" with Hardhat config is necesarry.