Koala theme - update node packages#2655
Merged
benderl merged 25 commits intoopenWB:masterfrom Aug 18, 2025
Merged
Conversation
benderl
force-pushed
the
update-node-packages
branch
from
5fb264e to
16c2b92
Compare
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
2 participants
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.
Veraltete Node-Pakete aktualisieren.
Ich habe die ESLint-Pakete nicht aktualisiert, da vite-plugin-checker ESLint 9 derzeit noch nicht unterstützt.
Ebenso habe ich TypeScript nicht aktualisiert, da TypeScript 5.9 @typescript-eslint v8 erfordert, welches wiederum ESLint 9 benötigt.
Solange vite-plugin-checker ESLint 9 nicht unterstützt, müssen wir bei ESLint 8 und TypeScript 5.5.
Quasar/app-vite 2.3.0 erfordert Node v20.
Die Aktualisierung von quasar-app-vite erforderte ein Paar Konfigurationsanpassungen.
Durch das Upgrade auf die neue Quasar-Version mit @quasar/app-vite@2 und dem neuen .quasar/tsconfig.json werden die TypeScript-Einstellungen strenger.
Typinkompatibilitäten Fehler, die vorher nicht aufgefallen sind – z.B. bei Chart.js und vue-chartjs, wo die Typen nicht 100% passen müsste behoben.
vue-chartjs gibt die Chart-Instanz als generisches Objekt zurück, TypeScript weiß aber nicht, dass das wirklich ein Chart.js-Objekt ist des wegen das Typecast.