GITARG

how'd you solve it @roker ?

I'm getting it to shut up about the non-exsistent error by utilizing a deprecated lib for now. Changed: ``` { "standard": { "parser": "@babel/eslint-parser" } } ``` from docs at...

Can an object ever be a useable parameter? The solidity ABI can only accept strings and number types?

Yeah, I'd like to know if the project is still active.

https://github.com/NomicFoundation/hardhat/blob/main/packages/hardhat-core/src/internal/solidity/compiler/downloader.ts https://github.com/NomicFoundation/hardhat/blob/f6c41e4f14bc7e246fb5da6110c25be8824e5d15/packages/hardhat-core/src/internal/solidity/compilation-job.ts#L6 https://github.com/NomicFoundation/hardhat/commit/ab34a7ba0fd979c462f37194aec97cea987aa8e3 https://github.com/NomicFoundation/hardhat/commit/220f2c88e13e392f7cfcf3ed944aed89dfa898ad

We need multiple cache dirs, one for each OS. Example(s): cache-v2 -> cache_macosx-amd64 ... ->cache_wasm or convention on ENUM pattern: cache-v2 -> cache-MACOS ... -> cache-WASM or lastly we have...

It already sort of does this: https://www.npmjs.com/package/env-paths running `npx hardhat compile` caches at `~/.cache/hardhat-nodejs/compilers-v2` like: linux-amd64 But that's redundant because of `path-env` package, The concept isn't because of compiler version....

lastly... We'll need to select the right version every time, but I think the current method does os.~whatever~ to get that `linux-amd64` POSIXish string.

https://github.com/NomicFoundation/hardhat/blob/c7890f0b75a685fc95c37693ecc76af3fd1c46fe/packages/hardhat-core/src/internal/solidity/compiler/downloader.ts#L112