@crimsonsunset/jsg-logger 1.8.4 → 1.8.6

package/CHANGELOG.md

@@ -5,6 +5,27 @@ All notable changes to the JSG Logger project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.8.6] - 2026-03-28 🪵 **configure() console feedback**
+
+### Changed
+- **`configure()` now logs applied config** — after merging the partial config, `configure()` emits a `"JSG Logger configured"` log entry showing `projectName`, `components`, and `timestampMode`. Previously the one-time init log fired at module evaluation time with default values, making it impossible to visually confirm that `configure()` had applied a consumer's `projectName` and other settings.
+
+---
+
+## [1.8.5] - 2026-03-28 🏷️ **configure() TypeScript types**
+
+### Added
+- **`configure()` TypeScript types** — `JSGLogger.configure(partialConfig?)` is now typed in `index.d.ts`. The method already existed in the JS implementation (1.8.4) but was missing from the type definitions, causing `any`-cast workarounds in consuming projects.
+
+### Migration
+Replace `JSGLogger.getInstanceSync(loggerConfig)` in post-init contexts (e.g. Next.js `instrumentation-client.ts`) with:
+```ts
+JSGLogger.configure(loggerConfig);
+```
+This merges config into the running singleton without triggering the reinit guard or wiping registered transports.
+
+---
+
 ## [1.8.3] - 2026-03-28 🔌 **addTransport() API**
 
 ### Added

package/index.d.ts

@@ -231,6 +231,29 @@ export interface JSGLogger {
    */
   getInstanceSync(config?: JSGLoggerConfig): LoggerInstanceType;
 
+  /**
+   * Update config on an already-initialized singleton without reinitializing.
+   * Merges the provided partial config into the running instance, preserving all
+   * registered transports. Use this instead of getInstanceSync(config) when the
+   * singleton may already be initialized by module-level auto-init.
+   *
+   * Emits a "JSG Logger configured" log showing the applied projectName and
+   * component count, so the final config is visible in the console even though
+   * the one-time init log already fired with defaults at module evaluation time.
+   *
+   * If the singleton has not yet been initialized, behaves like getInstanceSync(config).
+   *
+   * @param partialConfig - Partial config to merge into the running instance
+   * @returns The enhanced logger exports with controls API
+   *
+   * @example
+   * ```ts
+   * // instrumentation-client.ts — run before anything else uses the logger
+   * JSGLogger.configure({ projectName: 'My App', display: { timestamp: true } });
+   * ```
+   */
+  configure(partialConfig?: Partial<JSGLoggerConfig>): LoggerInstanceType;
+
   /**
    * Add a transport to the running singleton without reinitializing.
    * Safe to call even after the singleton was initialized by module-level code or a

package/index.js

@@ -999,8 +999,9 @@ class JSGLogger {
     /**
      * Update logger configuration post-initialization without reinitializing.
      * Merges partialConfig into the current config without touching registered transports.
-     * Transports can only be registered at init time — this method cannot add or remove them.
      * If called before any initialization has occurred, delegates to getInstanceSync(partialConfig).
+     * Emits a "JSG Logger configured" log so the applied project config is visible in the
+     * console even though the one-time init log already fired with defaults at module eval time.
      * @param {Object} partialConfig - Partial config to merge into the current config
      * @returns {Object} Enhanced logger exports
      */
@@ -1016,6 +1017,19 @@ class JSGLogger {
         JSGLogger._instance.transports = currentTransports;
         JSGLogger._instance.refreshLoggers();
 
+        // Re-log init summary so consumers can see the applied project config.
+        // The module-level auto-init fires before configure() can run, meaning
+        // the one-time init log always shows defaults. This follow-up makes
+        // the final configured state visible in the console.
+        if (JSGLogger._instance.loggers?.core) {
+            const components = configManager.getAvailableComponents();
+            JSGLogger._instance.loggers.core.info('JSG Logger configured', {
+                projectName: configManager.getProjectName(),
+                components: components.length,
+                timestampMode: configManager.getTimestampMode(),
+            });
+        }
+
         return JSGLogger._enhancedLoggers;
     }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@crimsonsunset/jsg-logger",
-  "version": "1.8.4",
+  "version": "1.8.6",
   "type": "module",
   "description": "Multi-environment logger with smart detection, file-level overrides, and beautiful console formatting. Test it live: https://logger.joesangiorgio.com/",
   "main": "index.js",