Achieve — High Level Logic Project. Creating a new meta design pattern.

Friendly in development. Fast in production. Just build your apps. Let Achieve do the rest.

← Back to technical specifications

Achieve Development Mode

Created November 6, 2026 · Updated November 6, 2026 · Achieve 3.1.0 · Qualified runtime: Node.js 24.22.2

Achieve defaults to development mode so application changes and request diagnostics are visible without restarting for every servlet edit. Production mode replaces repeated source checks with stable process-lifetime caches.

Selecting a mode

achieve.setMode("development"); // default
achieve.setMode("production");

Only those two exact values are accepted, and the choice must be made before a listener starts. Changing mode clears the production helper cache.

Development behavior

Development mode reports request flow, resolved URLs, resource and servlet activity, warnings, and errors to the console. Achieve reloads managed servlet source when its recorded modification time advances. Modules loaded through session.load() use corresponding development freshness checks.

Production behavior

Production mode suppresses routine development traces and caches resolved servlet modules and helper modules until process restart. Managed servlet error handling remains active; production mode does not turn exceptions into process crashes or disable configured access/server logging.

NODE_ENV and logging

Achieve mode is independent of process.env.NODE_ENV. setNodeEnv() changes that environment value for application code and packages but does not select Achieve's reload or diagnostic policy. Persistent logging is separately selected with setLogging().

Limits and verification

Reload detection is metadata-based and applies to Achieve-managed servlet/helper loading, not arbitrary modules imported and cached by application code. Detached asynchronous work remains application responsibility. Servlet-cache, helper-cache, load-module, logging, startup, and error suites verify development reload, production stability, diagnostics, mode validation, and continued error handling. See JavaScript Servlet Lifecycle and Logging in Achieve.