chatgpt-api VS dotenv

No problem at all :) Check out this github repo: https://github.com/transitive-bullshit/chatgpt-api

You can check out the chatgpt-api repository on GitHub. This API provides free access to ChatGPT https://github.com/transitive-bullshit/chatgpt-api

google for "chatgpt nodejs api" theres a couple things out there such as https://github.com/waylaidwanderer/node-chatgpt-api https://github.com/transitive-bullshit/chatgpt-api you might have to pay to use it though, or risk getting your account banned for using the free website preview thing

I just pushed an update to the `chatgpt` NPM package with support for the official ChatGPT API: https://github.com/transitive-bullshit/chatgpt-api

You forgot to give a link to this (well known in close circles) git: https://github.com/transitive-bullshit/chatgpt-api

Happy to answer any questions 👋 Check out the GitHub repo to get started: https://github.com/transitive-bullshit/chatgpt-api

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.