paul 193cadef27 Fix React error #130 and backend event creation ...

Frontend fixes:
- Disable verbatimModuleSyntax in TypeScript config to fix module imports
- Add displayName to critical React components for better production debugging
- Configure Vite build with manual chunks for better code splitting
- Enable sourcemaps for production debugging

Backend fixes:
- Remove updated_at field from events table insert (column doesn't exist)
- Fix SQL error that was causing 500 errors on event creation

These changes resolve:
- React error #130 that occurred during login and event creation
- 500 Internal Server Error when creating new events
- Better error tracking in production builds

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-07-07 13:30:53 +02:00

..

data

Fix React error #130 - Invalid element type

2025-07-07 11:19:59 +02:00

migrations

Replace all mock data with real backend integration

2025-07-06 22:46:24 +02:00

src

Fix React error #130 and backend event creation

2025-07-07 13:30:53 +02:00

.dockerignore

Add backend .dockerignore

2025-07-03 16:29:36 +02:00

.env.example

Add backend .env.example

2025-07-03 16:29:22 +02:00

.eslintrc.js

Add backend ESLint configuration

2025-07-03 16:29:50 +02:00

Dockerfile

Add backend Dockerfile

2025-07-03 16:29:04 +02:00

Dockerfile.dev

Implement complete frontend with admin panel and theme system

2025-07-06 22:04:45 +02:00

ecosystem.config.js

Add PM2 ecosystem configuration

2025-07-03 16:30:35 +02:00

jest.config.js

Add Jest configuration

2025-07-03 16:30:03 +02:00

jest.setup.js

Add Jest setup file

2025-07-03 16:30:20 +02:00

package-lock.json

Implement complete frontend with admin panel and theme system

2025-07-06 22:04:45 +02:00

package.json

Add backend package.json

2025-07-03 16:28:24 +02:00

server.js

Fix multiple production issues and add password change functionality

2025-07-07 10:25:38 +02:00