deps: update npm libraries for dependabot security fixes

[aaditkamat]

Summary by Sourcery

Update JavaScript dependencies to incorporate recent security and maintenance releases.

Enhancements:

• Refresh @opennextjs/cloudflare and wrangler runtime tooling to newer compatible versions.
• Update ESLint-related TypeScript and React hooks packages to the latest minor versions for improved linting and compatibility.

Build:

• Align devDependency versions in package.json and yarn.lock with updated tooling and security patches.

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates several npm dependencies and devDependencies (including Cloudflare integration, TypeScript ESLint tooling, Next.js ESLint config, React hooks ESLint plugin, and Wrangler) to newer versions to address Dependabot security advisories, with corresponding lockfile updates.

File-Level Changes

Change	Details	Files
Upgrade runtime Cloudflare and build/deployment tooling dependencies to patched versions.	Bump @opennextjs/cloudflare from ^1.19.6 to ^1.20.1 to pull in security and compatibility fixes. Bump wrangler from ^4.87.0 to ^4.110.0 for updated Cloudflare Workers tooling and security patches.	package.json yarn.lock
Upgrade linting and TypeScript-related devDependencies to newer, likely security-patched versions.	Bump @typescript-eslint/eslint-plugin from ^8.59.1 to ^8.63.0. Bump @typescript-eslint/parser from ^8.59.1 to ^8.63.0. Bump eslint-config-next from ^16.2.4 to ^16.2.10. Bump eslint-plugin-react-hooks from ^7.0.0 to ^7.1.1. Refresh yarn.lock to align transitive dependencies with the updated versions.	package.json yarn.lock

---

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.

[sourcery-ai]

Hey - I've left some high level feedback:

• Consider pinning wrangler to an exact version rather than using a caret range to avoid unexpected behavior changes in future CLI releases impacting your Cloudflare workflows.
• After bumping @typescript-eslint/* and eslint-config-next, double-check that your ESLint configuration does not reference any deprecated or renamed rules/options that might have changed between these versions.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider pinning `wrangler` to an exact version rather than using a caret range to avoid unexpected behavior changes in future CLI releases impacting your Cloudflare workflows.
- After bumping `@typescript-eslint/*` and `eslint-config-next`, double-check that your ESLint configuration does not reference any deprecated or renamed rules/options that might have changed between these versions.

---

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.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	eslint-config-next@​16.2.4 ⏵ 16.2.10
	@​typescript-eslint/​parser@​8.63.0
	@​typescript-eslint/​eslint-plugin@​8.63.0
	@​opennextjs/​cloudflare@​1.19.8 ⏵ 1.20.1			+1	-1
	wrangler@​4.87.0 ⏵ 4.110.0			+1

View full report