fix: Production-Build startet nicht (Vite 5→6 Regression)#54
Merged
Conversation
- storage-core/vite.tsm.config.ts: tsmPlugin ergänzt damit @eclipse-daanse/tsm korrekt externalisiert wird (kein Symbol-Mismatch bei @Injectable()) - ui-actions/builtinHandlers.ts: dynamisches import('@emfts/core') → statischer Import - ui-actions/index.ts: dynamisches import('@emfts/core') → statischer Import Ursache: Vite 6/7 änderte ESM-Bundle-Verhalten, TSM wurde in storage-core doppelt gebundelt → zwei Symbol-Instanzen → isInjectable() scheiterte. Außerdem: dynamische imports() werden nicht durch tsmPlugin transformiert.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Nach dem Vite 5→6 Upgrade via Dependabot startete die Production-App nicht mehr mit:
Class 'StorageAdapterRegistry' is not decorated with @injectable()Failed to resolve module specifier '@emfts/core'Ursache
Vite 6/7 änderte das ESM-Bundle-Verhalten:
@eclipse-daanse/tsmwurde instorage-corevollständig eingebundelt statt externalisiert. Das erzeugte zwei Symbol-Instanzen fürINJECTABLE_KEY— eine im Main-Bundle, eine in storage-core — wodurchisInjectable()immerfalsezurückgab.Außerdem wurden dynamische
import('@emfts/core')inui-actionsnicht durch dentsmPlugintransformiert und konnten im Browser nicht aufgelöst werden.Fix
storage-core/vite.tsm.config.ts:tsmPluginergänzt →@eclipse-daanse/tsmwird korrekt externalisiert, nur eine Symbol-Instanzui-actions/builtinHandlers.ts+index.ts: Dynamischeimport('@emfts/core')→ statische Imports (werden vom tsmPlugin korrekt transformiert)