DEV Community

Karthi Cedric
Karthi Cedric

Posted on

"I built a spell checker for backend configuration mistakes.”

Stop manually writing environment configs. Let your code do it for you.

Every backend developer has lived this nightmare:

You push to production on Friday afternoon. Saturday morning your phone explodes. The app is down. Users can't log in. The CEO is calling.

After 3 hours of debugging you find it.

One missing environment variable.

DATABASE_URL was set on your laptop. It was never configured in production.

This happens to every developer. Every company. Every week.

I built safelaunch to fix this

safelaunch is a CLI tool that catches environment mistakes before they reach production.

Install it:

npm install -g safelaunch
Enter fullscreen mode Exit fullscreen mode

The new feature: safelaunch init

The hardest part of adopting any new tool is setup. So I eliminated setup entirely.

Run this in any project:

safelaunch init
Enter fullscreen mode Exit fullscreen mode

safelaunch scans every .js .ts .jsx .tsx file in your project. Finds every process.env.VARIABLE reference. Generates your entire env.manifest.json automatically.

Output:

scanning project for environment variables...

found 3 environment variables:

  API_KEY
  DATABASE_URL
  REDIS_URL

created env.manifest.json
Enter fullscreen mode Exit fullscreen mode

Zero manual work. Zero friction. Your environment contract is generated from your actual code.

Then validate before you push 

safelaunch validate
Enter fullscreen mode Exit fullscreen mode

Output:

Running safelaunch...

❌ MISSING VARIABLES (2 found)

   DATABASE_URL   required but missing from .env
   REDIS_URL      required but missing from .env

✅ PASSING (1)

   API_KEY   present

Your environment is not ready for production.
Fix the issues above and run safelaunch again.
Enter fullscreen mode Exit fullscreen mode

You see exactly what will break before it breaks production.

Works in CI too

Add this to your GitHub Actions workflow to block bad deployments automatically:

- name: Install safelaunch
  run: npm install -g safelaunch

- name: Validate environment
  run: safelaunch validate
Enter fullscreen mode Exit fullscreen mode

If the environment contract is broken the deployment is blocked. No human decision required.

Try it 

npm install -g safelaunch
Enter fullscreen mode Exit fullscreen mode

Run safelaunch init in any Node.js project and tell me what it finds.

I'd love honest feedback. What would make this actually useful in your workflow?

Built by Orches. Backend Reliability Infrastructure.

npmjs.com/package/safelaunch

Top comments (0)