dotenv VS hardhat-deploy

We will put our Emailjs environment variables in a dotenv (.env) file. To read more about the purpose of this file click here.

Add .env to your .gitignore file to prevent it from being committed. Here's an example file with it already added. You may also use dotenv for advanced configuration and it will automatically load environment variables from a .env file into process.env.

dotenv: Designed to load environment variables from a .env file into the process.env environment

Like Doppler, Infisical uses environment variable injection. Similar to the Dotenv package for Node, when used in Node, it injects them at run time into the process object of the running app so they're not readable by any other processes or users. They can still be revealed by a crash dump or logging, so that is a caveat to consider in your code and build scripts.

We'll be working with databases' ids and different info that should be secured so I would advise you to create a .env file to store said info. We'll do this by installing dotenv into our project and use it accordingly:

dotenv - For reading our API keys from the environment

As an avid dotenv user I wanted to thank their maintainers for keeping the project alive for 10 years (wow). A perfect exemplary of dedication to Open Source.

Sensitive data like database URLs, API keys, and passwords should never be hardcoded in your application code. Instead, use environment variables accessed at runtime to keep this information secret. Popular dotenv libraries like dotenv make this easy for Node.js apps.

Attempting to implement this repository: https://github.com/wighawag/hardhat-deploy

or we can use the hardhat-deploy community plugin to deploy our contracts more professionally.

I imagine you have figured out how to do it by now. Consider using this plugin - https://github.com/wighawag/hardhat-deploy It will make your life easier and adds hre.getNamedAccounts() and hre.getUnnamedAccounts() Also it is exposed in the environment when running tests

Deploying consisted of using hardhat and its fantastic hardhat-deploy plugin to automagically manage deployments for us.

Next, lets install a package called hardhat-deploy which makes working with hardhat 2x easier & fun 👻

Hardhat-deploy now supports zkSync (Github)

Uses hardhat-deploy to keep track of deployments (upgradable or normal)

Once the hardhat project is initialized, Next we install hardhat-deploy which will make our life easier with deployments and tests😁

Install hardhat-deploy plugin as npm install hardhat-deploy and import it inside 'hardhat.config.js' file as:

Just found https://github.com/wighawag/hardhat-deploy, which is pretty much what I was looking for