Feed
Pro
Search

Sign in
FactoryKit - the AI software factory: tasks in, pull requests out Bug0 - The AI-native e2e QA regression testing The foreword by Hashnode - official blog from the Hashnode team Passmark - The open-source AI framework for regression testing Hashnode gql skill - let your AI agent publish to your Hashnode blog Hackathons Changelog Brand @hashnode on X Hashnode on LinkedIn Support - hello+support@hashnode.com Code of Conduct Terms Privacy Sitemap

Search Hashnode

Search posts, tags, users, and pages

FeedDiscussion

Aniket Dey

Jul 15

Stop Committing Secrets: Automatically Generate .env.example with gen-envex

When working on Node.js, React, Next.js, or any modern application, one of the first things you'll create is a .env file. It stores everything from database credentials to API keys and authentication

blog.aniketdey.in3 min read

#env #environment-variables #cli #dev #devtools #npm #opensource

Responses(3)

This is exactly the tool our team has been missing. Constantly forgetting to update .env.example has caused so many onboarding issues for new devs. Adding gen-envex to dev scripts is such a clean fix, appreciate you open-sourcing this! Such a clever solution to a trivial yet annoying problem. Preserving comments and line order while stripping secrets is perfect. Will install it immediately for all my Next.js projects. Great write-up too!

zi jie liu

Jul 17

Aniket Dey

Jul 17

Thank you so much! That means a lot to hear. 🙌

Hope it makes your Next.js projects a little smoother! If you have any feedback or ideas for improvements after trying it, I'd love to hear them. Thanks again for the support! ❤️

and please spread across the community and leave a ⭐ on the repo

Mayank Bansal

Jul 16

This is exactly the kind of thing runtime guardrails are for. I'm making Failproof AI, use policies to block access to sensitive files like .env before the agent ever gets to execute the read. It's completely open source just check out the repo of Failproof AI. Hit the star also if helpful :)