Implement Sentry error monitoring with PII protection

.eslintrc.json

@@ -2,10 +2,15 @@
   "extends": [
     "next/core-web-vitals",
     "eslint:recommended",
-    "plugin:@typescript-eslint/recommended",
     "plugin:prettier/recommended"
   ],
   "parser": "@typescript-eslint/parser",
   "plugins": ["@typescript-eslint", "prettier"],
-  "root": true
+  "root": true,
+  "overrides": [
+    {
+      "files": ["*.ts", "*.tsx"],
+      "extends": ["plugin:@typescript-eslint/recommended"]
+    }
+  ]
 }

.git-hooks/pre-push

@@ -0,0 +1,6 @@
+#!/bin/sh
+# Run lint before pushing to catch style/type issues early.
+# Bypass with: git push --no-verify
+
+echo "Running lint before push..."
+npm run lint

.gitignore

@@ -31,6 +31,9 @@ yarn-error.log*
 # vercel
 .vercel
 
+# sentry
+.env.sentry-build-plugin
+
 # typescript
 *.tsbuildinfo
 next-env.d.ts

next.config.js

@@ -1,5 +1,11 @@
+const { withSentryConfig } = require('@sentry/nextjs');
+
 /** @type {import('next').NextConfig} */
 const nextConfig = {
+  // Required on Next.js 14 so `src/instrumentation.ts` is loaded (stable in Next 15).
+  experimental: {
+    instrumentationHook: true,
+  },
   images: {
     remotePatterns: [
       {
@@ -22,4 +28,23 @@ const nextConfig = {
   },
 };
 
-module.exports = nextConfig;
+module.exports = withSentryConfig(nextConfig, {
+  // For all available options, see:
+  // https://www.npmjs.com/package/@sentry/webpack-plugin#options
+
+  org: 'tech-for-palestine',
+  project: 'ppm',
+
+  // Only print logs for uploading source maps in CI.
+  silent: !process.env.CI,
+
+  // Upload a larger set of source maps for prettier stack traces (increases build time).
+  widenClientFileUpload: true,
+
+  // Route browser requests to Sentry through a Next.js rewrite to circumvent
+  // ad-blockers. This can increase your server load as well as your hosting bill.
+  tunnelRoute: '/monitoring',
+
+  // Automatically tree-shake Sentry logger statements to reduce bundle size.
+  disableLogger: true,
+});