lesson-14

[TimeKeyRoll]

Does anyone know what is this all about? It suddenly stopped taking commands when i tried to test.

AND yes i did run npx clean which removed my artifacts and then i ran npm install and artifacts are still not back.

[TimeKeyRoll]

I think while getting artifacts back to folder could help to solve. So how do i get them back because npm install did not bring them back.

[RoboCrypter]

@TimeKeyRoll : You have to compile the contract in order to get the artifacts folder!

[TimeKeyRoll]

As we see in the screenshot i already tried to compile.

[ashrth]

@TimeKeyRoll try what @abossofmyself has mentioned and if it doesn't work you can also try checking this StackOverFlow question.

[TimeKeyRoll]

thanks

[krakxn]

@TimeKeyRoll

Since you already installed the dependencies, doing yarn hardhat compile (or npm equivalent) will generate the artifacts and cache folder for you.

However, please make sure the logic is correct else it will not compile.

[TimeKeyRoll]

As we see in the screenshot i already tried to compile.

[othaime-en]

Hey @TimeKeyRoll if you are working on windows, which I know you are, sometimes windows throws this error because you are using a global installation of hardhat instead of the local one that you installed in this specific folder. When you get this error, you normally can't run any commands thats why when you run npx hardhat compile you don't get any artifacts folder because you didn't compile anything. One remedy that I normally use is running the commands on wsl instead of the normal powershell.
If you have wsl installed, you can just run the command wsl on your command then try running the normal npx hardhat and npx hardhat compile commands
Try this and see if it works for you.

[krakxn]

Firstly, correct the logic; if it is correct, and running hardhat compile leads to the same error, then incorporate the above.

[TimeKeyRoll]

@othaime-en Appreciated reply. However i have been using powershell from the beginning of the course. It never caused the trouble. However this new folder HARDHAT-NFT-FCC created the trouble which was switched from hardhat-nft-fcc if you remember.
I am not sure what to do with it.

[TimeKeyRoll]

Firstly, correct the logic; if it is correct, and running hardhat compile leads to the same error, then incorporate the above.

Not sure what does that even mean?

[othaime-en]

I understand. I also ran into the same problem a couple months ago. I was using powershell okay but then one day I got the same error that you have above and when I switched to wsl it worked. But then a few weeks later, everything is working just fine. so you should try.

[TimeKeyRoll]

I am using old windows and i don't have any wsl. So not sure how and what to do with it. Sorry @othaime-en

[TimeKeyRoll]

I have run npm install --save hardhat and then tried npm install as well.now that error is gone but this new error is here.

[RoboCrypter]

@TimeKeyRoll : Can you make your terminal bigger and send me the full error screenshot from the beginning!

[TimeKeyRoll]

@abossofmyself @krakxn @othaime-en @ashrth Thankyou everyone
I fixed it. It is because when i run npx hardhat clean it actually wipped off all the package.json file so it had nothing in it . so i have had to redo everything. and it worked.