You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe. Hardhat recently added experimental support for ESM modules (alongside CJS) in TS projects. I played around with the 'template-ethereum-contracts' to try migrate it to ESM accordingly patching hardhat-deploy along the way.
Describe the solution you'd like
Would be great if hardhat-deploy could support loading of both CJS/ESM modules (depending on consuming project config).
Describe alternatives you've considered
While this patch does work for all cases (I can have a legcy full CJS project, I can leverage expremintal support to have scripts as either CJS or ESM using JS/TS), I'm not sure what would the correct way to properly implement it as part of hardhat-deploy with regards to restrictions still applying to hardhat and it's plugins and ESM.
Additional context
I see that hardhat team plans to further integrate ESM support into 'hardhat' itself and it's plugin eco-system (via 'ts-node' or maybe 'tsx'):
I am currently working on hardhat-deploy v2 I am using daily actually but not fully ready yet as I change stuff to suit my need still: see https://github.com/wighawag/rocketh
Is your feature request related to a problem? Please describe.
Hardhat
recently added experimental support for ESM modules (alongside CJS) in TS projects. I played around with the 'template-ethereum-contracts' to try migrate it to ESM accordingly patchinghardhat-deploy
along the way.Describe the solution you'd like
Would be great if
hardhat-deploy
could support loading of both CJS/ESM modules (depending on consuming project config).Describe alternatives you've considered
While this patch does work for all cases (I can have a legcy full CJS project, I can leverage expremintal support to have scripts as either CJS or ESM using JS/TS), I'm not sure what would the correct way to properly implement it as part of
hardhat-deploy
with regards to restrictions still applying to hardhat and it's plugins and ESM.Additional context
I see that
hardhat
team plans to further integrate ESM support into 'hardhat' itself and it's plugin eco-system (via 'ts-node' or maybe 'tsx'):The text was updated successfully, but these errors were encountered: