Lesson 15: Error: No Contract deployed with name NftMarketplace #1708
Replies: 3 comments 2 replies
-
is your front_end populated with NFT's when you mint and list? try |
Beta Was this translation helpful? Give feedback.
-
the --network localhost flag worked for me for the no contract deployed issue: For the tokenId part did you: 1 . run successfully the minting script?: 2 . if so, after the first run from cancel script the nft wont be listed and then it will fail: 3 . If that is not the case, because mint-and-list-item.js script could mint randomly one of two NFT contrats (BasicNftTwo or BasicNft) try to change on cancel-item.js script the getContract as follows: const basicNft = await ethers.getContract("BasicNftTwo") and change the const TOKEN_ID = XXX accordingly to the token minted equivalent to the run iteration (amount of scripts for minting runned) |
Beta Was this translation helpful? Give feedback.
-
you need to run blockchain in your local machine first
then run the below command on another terminal
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I created a file ( cancel-item.js ) inside scripts but as I run
yarn hardhat run scripts/cancel-item.js
I got this error:knowing that I named the contract
NftMarketplace.sol
and already deployed it.In the terminal running
yarn hardhat node
I got this error:
Beta Was this translation helpful? Give feedback.
All reactions