Hi. Advertising dotenvx etc. at runtime is the worst decision an OSS maintainer could possibly make. You’re honestly a strange person who shows no respect for the community and thinks you’ve created some kind of critical infrastructure library (#904 (comment)), while in reality you just wrote a simple .env parser + CLI support that any junior could reproduce in 25 minutes (and it would still be unnecessary). Since Node.js 20.12.0 there’s native API: process.loadEnvFile and util.parseEnv, which make dotenv completely obsolete today. Your whole “critical infra” narrative is nothing but pure ego inflation. You’re an anti-pattern for the open source community. You completely ignore feedback, and with every new comment you only sink your reputation further. I really don’t understand your reasoning. Every single one of your statements sounds unprofessional — don’t expect respect from the community if you don’t show any yourself.
This is a desperate attempt at monetization at the expense of millions of developers. Your idea of pushing ads into stdout and pretending they’re “helpful logs” shows a lack of respect for users and a total misunderstanding of the basics of UX in developer tooling.
Your module today is a relic, not some critical infrastructure. And instead of acting like a professional maintainer, you’re stuck in your own bubble of self-promotion and ego-boosting. Sad, because it shows that you no longer care about open source or the community, only about your own wallet. You act like a desperate influencer screaming: GIVE, GIVE, GIVE!
It should also be noted that your module is significantly slower than, for example, util.parseEnv. Someone even made an interesting benchmark here: https://www.npmjs.com/package/env-native#-benchmark-nodejs-v22170
Hi. Advertising dotenvx etc. at runtime is the worst decision an OSS maintainer could possibly make. You’re honestly a strange person who shows no respect for the community and thinks you’ve created some kind of critical infrastructure library (#904 (comment)), while in reality you just wrote a simple .env parser + CLI support that any junior could reproduce in 25 minutes (and it would still be unnecessary). Since Node.js 20.12.0 there’s native API:
process.loadEnvFileandutil.parseEnv, which make dotenv completely obsolete today. Your whole “critical infra” narrative is nothing but pure ego inflation. You’re an anti-pattern for the open source community. You completely ignore feedback, and with every new comment you only sink your reputation further. I really don’t understand your reasoning. Every single one of your statements sounds unprofessional — don’t expect respect from the community if you don’t show any yourself.This is a desperate attempt at monetization at the expense of millions of developers. Your idea of pushing ads into stdout and pretending they’re “helpful logs” shows a lack of respect for users and a total misunderstanding of the basics of UX in developer tooling.
Your module today is a relic, not some critical infrastructure. And instead of acting like a professional maintainer, you’re stuck in your own bubble of self-promotion and ego-boosting. Sad, because it shows that you no longer care about open source or the community, only about your own wallet. You act like a desperate influencer screaming: GIVE, GIVE, GIVE!
It should also be noted that your module is significantly slower than, for example, util.parseEnv. Someone even made an interesting benchmark here: https://www.npmjs.com/package/env-native#-benchmark-nodejs-v22170