AdonisJS 5 Env Module: No Automatic Reload During Development

The Current State of Env Loading

In AdonisJS 5, the Env module loads environment variables once during the application boot process via the @ioc:Adonis/Core/Env provider. These values are cached in memory for the duration of the process. Consequently, changes made to the .env file while the server is running are not reflected until the process is manually restarted.

Architectural Requirements for Auto-Reloading

To implement automatic reloading of environment variables without a full process restart, the following architectural changes would be required:

• Dynamic Binding: The Env provider would need to expose a reloadable binding that re-reads the .env file and updates the IoC container.
• Access Patterns: Services must call Env.get() dynamically during execution. Any service that assigns an environment variable to a local property during its boot or register phase will continue to use the stale value regardless of a reload.
• Watcher Integration: A lightweight file-watcher (using fs.watch or a library like chokidar) would need to monitor the .env file and trigger the reload hook upon a save event.

Interaction with Production Caching

This mechanism must remain strictly isolated to development. In production, the @adonisjs/assembler creates a configuration cache that inlines environment values into the build. An auto-reload feature would bypass this optimization and introduce unnecessary file system overhead, so it must be disabled when NODE_ENV is set to production.

Practical Implementation Strategy

If you require this behavior today, the most stable approach is to rely on the built-in development server's watch mode, which restarts the process on file changes. If you are building a custom watcher, follow these scoped steps:

1. Enable a Watcher: Implement a watcher that monitors the .env file.
2. Trigger Reload: Invoke a method within the Env provider to clear the internal cache and re-parse the file.
3. Verify Access: Ensure your code uses Env.get('KEY') inside request handlers rather than caching the value in a singleton service.

Verification: To test if a reload is working, create a temporary route that returns Env.get('SOME_VAR'). Change the value in .env and refresh the browser; if the value updates without a terminal restart, the reload was successful.

Diagnostic Detail Needed

Are you utilizing a process manager like PM2 in cluster mode during development? This would change the recommendation, as each cluster worker would attempt to watch the same file, potentially leading to race conditions and redundant CPU spikes.