Lesson 14: Error: ERROR processing 03-deploy-random-ipfs-nft.js

[mmuaaz]

Hello,
I have the error after I wrote the script for mint.js, before that I have tested all the other deploy scripts, I was not getting any errors, but now after adding mint.js script, I am facing strange errors, SS attached:

so, I have observed if I use :

const vrfCoordinatorV2Mock = await ethers.getContract("VRFCoordinatorV2Mock")
then I get error:
ReferenceError: vrfCoordinatorV2Mock is not defined

while If I use:
const vrfCoordinatorV2Mock = await deployments.get("VRFCoordinatorV2Mock")
then I get error:
TypeError: vrfCoordinatorV2Mock.createSubscription is not a function

I have checked all the spelling mistakes I may have missed something but I dont find any, please help
thank You

git Repo: https://github.com/mmuaaz/RandomNft-SolidityCourse

[RoboCrypter]

@mmuaaz : I have made a PR in your repo, Merge it and try it out!

And also add this version of Chainlink/Contracts, In your terminal run this command : yarn add @chainlink/contracts@0.4.0

After that recompile your contract and then deploy it!

Let me know, If it resolves your issue!

[mmuaaz]

and yeah I have downgraded the Chainlink version

[RoboCrypter]

@mmuaaz : I have made an other PR in your repo, Merge it, and try that out!

After Merging, That should fix this error : ( ReferenceError: vrfCoordinatorV2Mock is not defined )

Let me know, If it resolves your issue!

[mmuaaz]

ok let me try

[mmuaaz]

Thank You Sir, its been like 20th time you helped me, thank you very much

[RoboCrypter]

@mmuaaz : Most Welcome!

[JamesMckenna]

Can you run "yarn hardhat deploy/03-deploy-random-ipfs-nft.js" without errors?

Ensure: const vrfCoordinatorV2Mock = await ethers.getContract("VRFCoordinatorV2Mock")
Then move the 04-mint.js file to it's own directory. projectRoot>scripts>04-mint.js
For your convenience, I would recommend renaming to mint.js

Then try "yarn hardhat deploy".

Does that fix the issue? Can you now deploy without errors?

[mmuaaz]

Bro the issue is resolved, I think its the chainlink version that is causing the error, downgrading it solves the issue