fastify-auth VS dotenv

100% compatibility with already built fastify plugin, so things like authentication can be done in an already good way, like with fastify-auth

Fastify as its core is okay. Not great, but OK. But plugins (official ones) made me struggle. For example, I couldn't figure out how to get fastify-auth plugin to work. It seems like plugins, even official, do not keep the same standards across whole ecosystem. It would be nice if all would have TS examples.

So the example is here I copied it as is, just adapting routes. Now to my understanding, I need either sessions or cookies so that when the user hits only one time ` http://127.0.0.1:3000/auth-multiple` all sequential calls to any secured api would verify the token.

For example, Fastify allows us to write better and cleaner asynchronous code by parsing JSON requests. With Fastify plugins, you don’t have to install multiple npm packages from different authors to perform common tasks like authentication and validation.

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.