@zambon-dev/framework 1.3.0 → 1.3.1

package/CHANGELOG.md

@@ -23,6 +23,27 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### ⚠ Breaking Changes / Migration
 
+## [1.3.1] - 2026-09-10
+
+### Fixed
+
+- **Returning to an already-open tab no longer crashes with `Maximum call stack size exceeded`.**
+  It affected any screen whose route nests two empty-path levels — the shape every list screen uses:
+  `path: ''` with `DefaultTabViewComponent`, and a child `path: ''` with the list component.
+
+  `CustomReuseStrategy` keyed its detached-view cache on `route.component.name`, and a production
+  build renames every class: esbuild wraps each component as `X = (() => { class i { } return i; })()`,
+  so the name is one mangled letter that the whole chunk shares. An empty path contributes no URL
+  segment, so both levels also resolved to the same URL — which left the two cache keys identical.
+  Storing one handle overwrote the other, both route levels were then handed the same detached view,
+  and Angular blew the stack building a router state whose node was its own descendant.
+
+  The key is now built from the component's **identity** and the route's depth rather than its name.
+  Applications need to change nothing. Worth knowing when reading old reports of this crash: it only
+  ever reproduced in a minified build — `ng serve` keeps real class names — and only on the screens
+  whose chunk happened to mangle to the same letter as the framework's, so a rebuild could move the
+  symptom from one screen to another.
+
 ## [1.3.0] - 2026-07-30
 
 ### Added
@@ -121,7 +142,8 @@ None.
   available via [GitHub Releases](https://github.com/RicardoZambon/ZLibraries/releases) and the
   `framework-v*` tags.
 
-[Unreleased]: https://github.com/RicardoZambon/ZLibraries/compare/framework-v1.3.0...HEAD
+[Unreleased]: https://github.com/RicardoZambon/ZLibraries/compare/framework-v1.3.1...HEAD
+[1.3.1]: https://github.com/RicardoZambon/ZLibraries/releases/tag/framework-v1.3.1
 [1.3.0]: https://github.com/RicardoZambon/ZLibraries/releases/tag/framework-v1.3.0
 [1.2.1]: https://github.com/RicardoZambon/ZLibraries/releases/tag/framework-v1.2.1
 [1.2.0]: https://github.com/RicardoZambon/ZLibraries/releases/tag/framework-v1.2.0

package/fesm2022/zambon-dev-framework.mjs

@@ -121,6 +121,8 @@ let CustomReuseStrategy = class CustomReuseStrategy {
     tabService;
     applicationRef = inject(ApplicationRef);
     cachedHandles = {};
+    componentIDs = new WeakMap();
+    nextComponentID = 1;
     //#endregion
     //#region Properties
     //#endregion
@@ -193,8 +195,39 @@ let CustomReuseStrategy = class CustomReuseStrategy {
         if (this.clones[url]) {
             url = this.clones[url];
         }
-        const componentName = route.component?.name ?? '';
-        return `${url}-${componentName}`;
+        // The component is identified by identity, never by name. A production build renames every
+        // class: esbuild wraps each component as `X = (() => { class i { } return i; })()`, so
+        // `component.name` is a single mangled letter that the whole chunk shares. Nested empty-path
+        // routes already resolve to the same URL, because an empty path contributes no segment, so a
+        // key built from the name collapsed a screen's tab view and its list into one entry: storing
+        // one overwrote the other, both levels were then handed the same detached view, and Angular
+        // blew the stack building a router state whose node was its own descendant. That reproduced
+        // only in a minified build, and only on the screens whose chunk happened to mangle to the
+        // same letter as the framework's.
+        //
+        // The depth is part of the key too, so two sibling routes sharing a component type under one
+        // URL cannot collide either.
+        return `${url}-${this.getRouteDepth(route)}-${this.getComponentID(route.component)}`;
+    }
+    getComponentID(component) {
+        if (typeof component !== 'function') {
+            return 0;
+        }
+        let componentID = this.componentIDs.get(component);
+        if (componentID === undefined) {
+            componentID = this.nextComponentID++;
+            this.componentIDs.set(component, componentID);
+        }
+        return componentID;
+    }
+    getRouteDepth(route) {
+        let depth = 0;
+        let current = route.parent;
+        while (current) {
+            depth++;
+            current = current.parent;
+        }
+        return depth;
     }
     getUrlFromRoute(route) {
         const segments = [];