Published new packages

[K-Ho]

Description

Updated package.json files for newly published packages

Questions

Question for @kfichter - can we make the contracts and ovm-toolchain packages public?

Fixes

• Fixes #YAS-632

Contributing Agreement

• I have read and understood the Optimism Contributing Guide and Code of Conduct and am following those guidelines in this pull request.

[smartcontracts]

Question for @kfichter - can we make the contracts and ovm-toolchain packages public?

This is a serious headache right now caused by quirks within buidler. buidler expects both plugins and typescript/ts-node to exist within the same node_modules folder as buidler itself (which is a bit silly, to be honest). yarn hoisting packages up to the root to reduce dependencies ends up breaking buidler. So we have to use the nohoist option in our package.json files, which only works if private: true.

I haven't checked recently see if this has been solved. I'll make an issue on buidler if not. We could possibly use symlinks to trick buidler into working correctly, but that's a bit hacky.

[karlfloersch]

Hot 🔥 right here. Merrrrrge-able!

[karlfloersch]

What do we export these for btw?

[K-Ho]

for the cross domain contracts see -> https://github.com/ethereum-optimism/Buidler-Deposit-Withdraw-Example/blob/abb04077f1f239b78d5677af3f2fdcf1f545ce9e/contracts/ERC20/DepositedERC20.sol#L4