Feature/sentry error logging #5

Merged
Sluijsens merged 11 commits from feature/sentry_error_logging into master 2026-07-25 20:04:18 +02:00
4 changed files with 17 additions and 19 deletions
Showing only changes of commit 708d89905c - Show all commits
+5
View File
@@ -7,6 +7,11 @@ dist-ssr
# TypeScript incremental build cache (local-only, regenerated on every build) # TypeScript incremental build cache (local-only, regenerated on every build)
tsconfig.tsbuildinfo tsconfig.tsbuildinfo
tsconfig.node.tsbuildinfo
# vite.config.js is emitted next to vite.config.ts by `tsc -b` (tsconfig.node.json has
# no outDir/noEmit), so it is a regenerated build artifact, not source.
vite.config.js
# Logs # Logs
*.local *.local
@@ -540,3 +540,15 @@
**Context**: Post-workflow follow-up (feature already marked Complete); continues the `feature/sentry_error_logging` branch. `pnpm run build`, `pnpm run lint` and `pnpm run test` re-verified successfully after the change. Changes not yet committed/pushed. **Context**: Post-workflow follow-up (feature already marked Complete); continues the `feature/sentry_error_logging` branch. `pnpm run build`, `pnpm run lint` and `pnpm run test` re-verified successfully after the change. Changes not yet committed/pushed.
--- ---
## Post-Completion Follow-up: Regenerated Build Artifacts Removed from Git Tracking
**Timestamp**: 2026-07-25T15:47:00Z
**User Input**: "ik wil niet dat er wijzigingen open blijven staan lokaal. zorg dat je ze mee-commit of ignored. Als het nodig is maak je een lokale versie die ignored moet worden."
**AI Response**: "Investigated the two remaining locally-modified files (`tsconfig.node.tsbuildinfo`, `vite.config.js`) and confirmed both are build artifacts regenerated by `tsc -b` (per `tsconfig.node.json`, which has no `outDir`/`noEmit`, `vite.config.ts` gets compiled to `vite.config.js` right next to it, and its own incremental-build cache is `tsconfig.node.tsbuildinfo`) — neither is source, so committing their contents would just cause perpetual diff noise. Removed both from git tracking (`git rm --cached`) and added them to `.gitignore` alongside the already-ignored `tsconfig.tsbuildinfo`, so they remain on disk (needed for `tsc -b` to work) but are never tracked again."
**Context**: Post-workflow follow-up (feature already marked Complete); continues the `feature/sentry_error_logging` branch, ensuring no local changes are left uncommitted/untracked.
---
File diff suppressed because one or more lines are too long
-18
View File
@@ -1,18 +0,0 @@
/// <reference types="vitest/config" />
import { defineConfig } from 'vite';
import react from '@vitejs/plugin-react';
import { version } from './package.json';
// https://vitejs.dev/config/
export default defineConfig({
plugins: [react()],
define: {
// Injected at build time, used as the Sentry `release` tag (see src/main.tsx).
__APP_VERSION__: JSON.stringify(version),
},
test: {
environment: 'jsdom',
globals: true,
setupFiles: './src/test/setup.ts',
css: true,
},
});