Fetch Source via URL (Github, Soucify, etc)

[0xCourtney]

reference: #6 (comment)

[ItsNickBarry]

If bytecode is published to GitHub or similar, it can be added as an NPM dependency. Then, is there any reason to re-export it?

[0xCourtney]

If bytecode is published to GitHub or similar, it can be added as an NPM dependency. Then, is there any reason to re-export it?

I didn't really explain this but I was thinking that the plugin would fetch the source and then export the bytecode. Otherwise, I agree if the bytecode is already available somewhere it doesn't make sense to export it again.

[ItsNickBarry]

This should be a feature of hardhat-dependency-compiler instead. If that plugin could download contract source code from a URL or by address from a blockchain explorer, then the compilation artifacts would be available not only to this plugin but also to hardhat-abi-exporter and hardhat-ethers (for deployment purposes).

Anyway, in the particular case of bytecode extraction, it's fairly simple to just use the eth_getCode RPC method.

Closing this in favor of this: ItsNickBarry/hardhat-dependency-compiler#22