Add React 19 support and fix TypeScript issues

- Add React 19 to peerDependencies
- Update testing libraries to latest versions
- Fix TypeScript errors in Dropzone component
- Improve error handling for undefined values
- Add proper type checking for File objects

Author: phDooY

.cursorrules

@@ -0,0 +1,48 @@
+
+You are an expert in TypeScript, Gatsby, React and Tailwind.
+
+Code Style and Structure
+
+- Write concise, technical TypeScript code.
+- Use functional and declarative programming patterns; avoid classes.
+- Prefer iteration and modularization over code duplication.
+- Use descriptive variable names with auxiliary verbs (e.g., isLoaded, hasError).
+- Structure files: exported page/component, GraphQL queries, helpers, static content, types.
+
+Naming Conventions
+
+- Favor named exports for components and utilities.
+- Prefix GraphQL query files with use (e.g., useSiteMetadata.ts).
+
+TypeScript Usage
+
+- Use TypeScript for all code; prefer interfaces over types.
+- Avoid enums; use objects or maps instead.
+- Avoid using `any` or `unknown` unless absolutely necessary. Look for type definitions in the codebase instead.
+- Avoid type assertions with `as` or `!`.
+
+Syntax and Formatting
+
+- Use the "function" keyword for pure functions.
+- Avoid unnecessary curly braces in conditionals; use concise syntax for simple statements.
+- Use declarative JSX, keeping JSX minimal and readable.
+
+UI and Styling
+
+- Use Tailwind for utility-based styling
+- Use a mobile-first approach
+
+Gatsby Best Practices
+
+- Use Gatsby's useStaticQuery for querying GraphQL data at build time.
+- Use gatsby-node.js for programmatically creating pages based on static data.
+- Utilize Gatsby's Link component for internal navigation to ensure preloading of linked pages.
+- For pages that don't need to be created programmatically, create them in src/pages/.
+- Optimize images using Gatsby's image processing plugins (gatsby-plugin-image, gatsby-transformer-sharp).
+- Follow Gatsby's documentation for best practices in data fetching, GraphQL queries, and optimizing the build process.
+- Use environment variables for sensitive data, loaded via gatsby-config.js.
+- Utilize gatsby-browser.js and gatsby-ssr.js for handling browser and SSR-specific APIs.
+- Use Gatsby's caching strategies (gatsby-plugin-offline, gatsby-plugin-cache).
+
+Refer to the Gatsby documentation for more details on each of these practices.
+    

jest.config.js

@@ -1,14 +1,18 @@
-const config = {
-  roots: ["<rootDir>/tests"],
+module.exports = {
+  testEnvironment: 'jsdom',
   transform: {
-    "^.+\\.tsx?$": "ts-jest",
+    '^.+\\.(ts|tsx)$': [
+      'ts-jest',
+      {
+        tsconfig: 'tsconfig.json',
+        isolatedModules: true,
+        diagnostics: {
+          ignoreCodes: [151001]
+        }
+      }
+    ]
   },
-  preset: "ts-jest",
-  testRegex: "(/__tests__/.*|(\\.|/)(test|spec))\\.tsx?$",
-  moduleFileExtensions: ["ts", "tsx", "js", "jsx", "json", "node", "d.ts"],
   moduleNameMapper: {
-    "^.+\\.(css|less|scss)$": "identity-obj-proxy",
-  },
-  testEnvironment: "jsdom",
+    '\\.(css|less|scss|sass)$': 'identity-obj-proxy'
+  }
 };
-module.exports = config;