@ti-engine/core 1.11.1 → 1.12.0

package/CHANGELOG.md

@@ -2,6 +2,17 @@
 
 This document contains the list of changes made to the framework. The format is based on the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification.
 
+## Version 1.12.0
+
+* feat(start-instance): report which `.env` file was loaded, or that none was found at the resolved path, at `DEBUG`.
+  The path is derived from `process.cwd()`, and a missing file is deliberately not fatal — a container legitimately
+  supplies its whole environment directly. But the two cases were indistinguishable: an instance started from a
+  different working directory (an IDE run configuration, a wrapper script) read no env file at all, and every
+  setting it carried was simply absent. That surfaces much later as behaviour nobody configured — an empty
+  allowlist, an unset secret — with nothing linking it back to a file that was never read. The outcome is logged
+  just after the logger becomes available, since loading the logger any earlier would pull in configuration that
+  reads `process.env`.
+
 ## Version 1.11.1
 
 License change only — no functional code changed.

package/bin/start-instance.js

@@ -40,8 +40,16 @@ const envFilePath = ( () => {
 
 // Load the resolved .env file using the native Node loader (Node >= 20.12). A missing file is not fatal —
 // environment variables may be supplied entirely by the OS/container. Existing process.env values are NOT overridden.
+//
+// Whether it was found is recorded rather than discarded. The path is derived from process.cwd(), so an instance
+// started from a different working directory — an IDE run configuration, a wrapper script — silently reads no env
+// file at all, and every setting it carried is simply absent. That surfaces much later as behaviour nobody
+// configured, with nothing linking it back to the file that was never read. The logger cannot be required yet
+// (loading it pulls in configuration that reads process.env), so the outcome is logged a few lines down.
+let envFileLoaded = false;
 try {
     process.loadEnvFile( envFilePath );
+    envFileLoaded = true;
 } catch ( error ) {
     if ( error.code !== "ENOENT" ) {
         throw error;
@@ -51,6 +59,10 @@ try {
 const tools = require( "#tools" );
 const logger = require( "#logger" );
 
+logger.log( envFileLoaded
+    ? `Loaded environment variables from '${ envFilePath }'.`
+    : `No environment file at '${ envFilePath }' — continuing with the environment as supplied. If settings you expected are missing, check the working directory this instance was started from.`, logger.logSeverity.DEBUG );
+
 // Configure the current instance variables before requiring any platform modules and store the necessary ones in memory cache:
 process.env.TI_INSTANCE_ID = "ti-" + tools.getUUID();
 process.env.TI_INSTANCE_CLASS = process.env.TI_INSTANCE_CLASS || "";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ti-engine/core",
-  "version": "1.11.1",
+  "version": "1.12.0",
   "description": "Microservice framework for Node.js: a Redis-backed message exchange with end-to-end call tracing, retries and tamper-evident message envelopes.",
   "keywords": [
     "microservices",