fix: package.json to reduce vulnerabilities (#7)

[Dargon789]

Summary by Sourcery

Enhancements:

• Upgrade Next.js, React, Zod, Playwright test runner, and TypeScript to newer minor versions for improved stability and security.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates several core runtime and tooling dependencies (Next.js, React, Zod, Playwright, and TypeScript) to newer patch/minor versions to address known vulnerabilities, with corresponding lockfile updates.

File-Level Changes

Change	Details	Files
Bump runtime dependencies to newer secure versions.	Update Next.js from 15.3.8 to 16.0.10. Update React from 19.1.0 to 19.2.0 while keeping react-dom at 19.1.0. Update Zod from 3.25.76 to 4.2.1. Ensure package.json reflects the new versions for application runtime packages.	package.json package-lock.json
Bump dev/test tooling to newer secure versions.	Update Playwright test runner from 1.54.1 to 1.55.1. Update TypeScript from 5.8.3 to 5.9.3. Ensure package.json and lockfile are aligned with new devDependency versions.	package.json package-lock.json

Possibly linked issues

• [Snyk] Security upgrade @playwright/test from 1.54.1 to 1.55.1 #7: PR includes the requested @playwright/test 1.54.1→1.55.1 security upgrade, matching the issue, plus additional dependency bumps.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gemini-code-assist]

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request systematically updates a range of project dependencies, primarily targeting 'next', 'zod', 'react', 'next-auth', and 'sharp', to mitigate known vulnerabilities and leverage the latest improvements. The updates also reflect a shift in the required Node.js runtime environment and a general cleanup of the dependency graph, ensuring a more secure and modern development setup.

Highlights

• Major Dependency Upgrades: Key packages such as 'next', 'zod', 'react', 'next-auth', and 'sharp' have been updated to their latest versions, addressing potential vulnerabilities and introducing new features and improvements.
• Node.js Engine Requirement Update: The minimum Node.js version required for the project has been raised to '>=20.9.0', aligning with the updated 'next' framework and ensuring compatibility with modern runtime features.
• Dependency Clean-up and Optimization: Several unused or transitive dependencies, including 'busboy', 'color', 'is-arrayish', and others, have been removed from 'package-lock.json', streamlining the dependency tree and potentially reducing bundle size.
• Platform-Specific Sharp Updates: All platform-specific 'sharp' and 'sharp-libvips' packages have been updated, including the addition of 'riscv64' support, enhancing image processing capabilities across various architectures.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[sourcery-ai]

Hey - I've left some high level feedback:

• React was bumped to 19.2.0 but react-dom remains at 19.1.0; consider updating react-dom to the same version to avoid subtle compatibility issues.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- React was bumped to 19.2.0 but react-dom remains at 19.1.0; consider updating react-dom to the same version to avoid subtle compatibility issues.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request aims to reduce vulnerabilities by upgrading several dependencies. While the intent is good, there are critical inconsistencies between package.json and package-lock.json. Several dependencies updated in package.json are not reflected in package-lock.json, and vice-versa. Additionally, react and react-dom versions are out of sync. I've provided a suggestion to fix some of the version mismatches in package.json and recommend running npm install to regenerate the lock file and ensure all dependencies are correctly resolved and locked.

[gemini-code-assist]

There are some inconsistencies with dependency versions that need to be addressed.

1. next-auth is updated to 5.0.0-beta.30 in package-lock.json, but it's still 5.0.0-beta.29 here. It should be updated to match.
2. react is updated to 19.2.0, but react-dom is still at 19.1.0. It's highly recommended to keep react and react-dom versions in sync to avoid subtle bugs.

After updating these, please run npm install to ensure package-lock.json is correctly updated and commit the changes. The current package-lock.json is out of sync with package.json for react, @playwright/test, and typescript as well, which will be fixed by regenerating the lock file.

Suggested change

	"next-auth": "5.0.0-beta.29",
	"next-themes": "0.4.6",
	"react": "19.1.0",
	"react": "19.2.0",
	"react-dom": "19.1.0",
	"next-auth": "5.0.0-beta.30",
	"next-themes": "0.4.6",
	"react": "19.2.0",
	"react-dom": "19.2.0",