When publishing a new contract, oftentimes I run into
Do you want to publish this package under the resource account's address 0xca...? [yes/no] >
yes
package size 17138 bytes
{
"Error": "Simulation failed with status: Move abort in 0x1::code: EPACKAGE_DEP_MISSING(0x60005): Dependency could not be resolved to any published package."
}
It takes quite some effort in order to figure out which exact dependency is not missing. Would be great if we can get something like below to improve DevX
Do you want to publish this package under the resource account's address 0xca...? [yes/no] >
yes
package size 17138 bytes
{
"Error": "Simulation failed with status: Move abort in 0x1::code: EPACKAGE_DEP_MISSING(0x60005): Dependency could not be resolved to any published package."
}
Dependency FixedPoint64 cannot be found at address 0xabc
Motivation
Is your feature request related to a problem? Please describe.
Pitch
Describe the solution you'd like
Describe alternatives you've considered
Are you willing to open a pull request? (See CONTRIBUTING)
🚀 Feature Request
When publishing a new contract, oftentimes I run into
It takes quite some effort in order to figure out which exact dependency is not missing. Would be great if we can get something like below to improve DevX
Motivation
Is your feature request related to a problem? Please describe.
Pitch
Describe the solution you'd like
Describe alternatives you've considered
Are you willing to open a pull request? (See CONTRIBUTING)
Additional context