Is your feature request related to a problem? Please describe.
Vs code is able to read and apply type annotations so that interacting with the hre object becomes more fluid in Javascript language
Describe the solution you'd like
I would like to have the same autocompletion and Intellisense functionality as shown in the picture:
For example say you have a bunch of deployment scripts following the pattern:
But not all developers will be doing that because maybe they are not aware of this possibility or for any other reason will not do it.
So ideally the type annotation should be applied on hardhat-deploy in a way there would be no need to add the type annotations here.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
It would be also nice to have the ability to process .mjs and .cjs deployment scripts in deploy folder. Or to make the entire package modular with "type": "module" in package.json to process esm code in .js files within deploy folder just like node does.
Is your feature request related to a problem? Please describe. Vs code is able to read and apply type annotations so that interacting with the
hre
object becomes more fluid in Javascript languageDescribe the solution you'd like I would like to have the same autocompletion and Intellisense functionality as shown in the picture:![image](https://github.com/wighawag/hardhat-deploy/assets/152483245/0ff07db7-b5db-4dd5-b0df-24adec211989)
For example say you have a bunch of deployment scripts following the pattern:
Currently a developer would have to edit it to:
But not all developers will be doing that because maybe they are not aware of this possibility or for any other reason will not do it. So ideally the type annotation should be applied on hardhat-deploy in a way there would be no need to add the type annotations here.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context It would be also nice to have the ability to process .mjs and .cjs deployment scripts in deploy folder. Or to make the entire package modular with "type": "module" in package.json to process esm code in .js files within deploy folder just like node does.