this post was submitted on 18 Aug 2023
30 points (100.0% liked)
Programming
423 readers
10 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
dotenv has lots of features and I doubt node will try to match all of them.
The builtin node feature needs you to specify .env files as parameters to the node executable and puts values in
process.env, that's it. It's great if that's all you need.With dotenv (which should've been called dotini) you can choose a file (any file, not just .env) to parse programatically, you can parse variables, you can specify the encoding and the override behavior, you can enable debugging, you can put the values in a different variable from
process.env, you can do decryption, and it supports multiline values.Last but not least,
process.envwas supposed to contain actual environment variables. Patching it with values from config files and mixing up the two concepts is a mistake โ but at least dotenv lets you avoid it. With dotenv you can read from .config and put the values inprocess.config; with the node version you can read from .config files (at least I hope you'll be able to) but it goes toprocess.envwhether you like it or not.