vitest 2.0.5 -> 5.0.1 in allen betroffenen Apps (dms-browser, dms-upload, kennzahlen-dashboard, mail-search, retention-admin, pdf-viewer) sowie shl (CI-Matrix). pdf-viewer zusaetzlich jsdom 24 -> 29 (entfernt canvas/tar-Kette). @types/node auf 22 gehoben (vitest-5-Peer-Dependency), @testing-library/jest-dom auf 7.0.1 (vitest-5-Typaugmentierung), esbuild.jsx-Workaround in vitest.config.ts entfernt (von Vite/esbuild-Option-Konflikt, ueberfluessig seit tsconfig jsx bereits react-jsx setzt). Neue vitest.d.ts in dms-browser/pdf-viewer fuer jest-axe-Matcher-Typisierung (@types/jest-axe augmentiert Jest-Namespace, nicht Vitest 5s Assertion-Interface). 0 verbleibende npm-audit-Funde in allen 7 Paketen (vorher 4-10 je App). Nur Entwicklungsabhaengigkeiten betroffen, kein Produktionsrisiko. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
30 lines
668 B
JSON
30 lines
668 B
JSON
{
|
|
"name": "nexarch-dms-browser",
|
|
"private": true,
|
|
"scripts": {
|
|
"dev": "next dev",
|
|
"build": "next build",
|
|
"start": "next start",
|
|
"test": "vitest run"
|
|
},
|
|
"dependencies": {
|
|
"@nexarch/shl": "file:../shl",
|
|
"next": "16.3.5",
|
|
"react": "19.3.0",
|
|
"react-dom": "19.3.0"
|
|
},
|
|
"devDependencies": {
|
|
"@testing-library/react": "16.3.3",
|
|
"@types/jest-axe": "^3.5.9",
|
|
"@types/node": "^22.20.4",
|
|
"@types/react": "19.3.0",
|
|
"@types/react-dom": "19.3.0",
|
|
"@vitest/coverage-v8": "^5.0.1",
|
|
"axe-core": "^4.13.0",
|
|
"jest-axe": "^11.0.0",
|
|
"jsdom": "24.1.0",
|
|
"typescript": "5.5.3",
|
|
"vitest": "^5.0.1"
|
|
}
|
|
}
|