Lesson 5: How the system recognize PRIVATE_KEY_PASSWORD on command line as part of .env if we deleted it?

[eli5mecoding]

Why PRIVATE_KEY_PASSWORD:password once executed on command line, is readed as if there was still a PRIVATE_KEY_PASSWORD on .env file if we deleted it?

The code below in my understanding is saying: process env to check for the PRIVATE_KEY_PASSWORD, isn't it? Like, check for the PRIVATE_KEY_PASSWORD on .env file?

   let wallet = new ethers.Wallet.fromEncryptedJsonSync(
   encryptedJson,
   process.env.PRIVATE_KEY_PASSWORD
 );

but there's no PRIVATE_KEY_PASSWORD there since we deleted it.

How typing PRIVATE_KEY_PASSWORD=password on command line add it to .env?

Video part: https://youtu.be/gyMwXuJrbJQ?t=28050

[technophile-04]

Hey, I think you got it wrong process.env does not read the .env file and populates the fields.

The process core module of Node.js provides the env property which hosts all the environment variables that were set at the moment the process was started.

You can set env property while running a particular node file
example : NAME=SHIV node deploy.js this populates process.env.NAME with SHIV

Now, coming to .env file, To populate the variables from this file we have used a package called dotenv and we have configured it at the start of our script. This dotenv is what takes your variables from .env file and add them to process.env .

Conclusion :
You can always set env property without .env file by just specifying them while running the script.
eg : NAME=SHIV node deploy.js

To use .env file so that we don't want to always specify env variables always while running script we use package dotenv while takes varibales from .env file and poplulates our env propety

[eli5mecoding]

This all makes sense, now I undertand! Thank you