Added @eslint/eslintrc to devDependency

[WazirRohiman]

PR fixes a bug where a fresh project setup would fail during the pre-commit lint check.

Changes

• Added @eslint/eslintrc to the devDependencies in nextjs-frontend/package.json.

Reason
The nextjs-frontend/eslint.config.mjs file imports { FlatCompat } from "@eslint/eslintrc", but this package was
not listed as a dependency in devDependencies. This caused the pnpm run lint command and the pre-commit hook to fail with a "Cannot
find package" error. Adding the dependency resolves this issue.

Summary by Sourcery

Add the missing @eslint/eslintrc dependency to the Next.js frontend to restore successful lint and pre-commit checks

Bug Fixes:

• Add @eslint/eslintrc to devDependencies in package.json to resolve missing package errors during linting

Enhancements:

• Update pnpm-lock.yaml to bump @eslint/eslintrc to version 3.3.1

[sourcery-ai]

Reviewer's Guide

This PR resolves lint failures on new setups by adding the missing “@eslint/eslintrc” package to devDependencies and updating the lockfile entries to version 3.3.1.

File-Level Changes

Change	Details	Files
Added missing ESLint config package as a dev dependency	Inserted “@eslint/eslintrc”: “^3.3.1” under devDependencies in package.json Added specifier and version entries under importers.devDependencies in pnpm-lock.yaml	nextjs-frontend/package.json nextjs-frontend/pnpm-lock.yaml
Bumped “@eslint/eslintrc” lockfile resolution to 3.3.1	Updated resolution version from 3.2.0 to 3.3.1 Refreshed integrity hashes in resolution and snapshot sections	nextjs-frontend/pnpm-lock.yaml

Possibly linked issues

• #123: PR adds missing @eslint/eslintrc dependency to package.json, fixing the lint failure described in the issue.

---

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 @WazirRohiman - I've reviewed your changes and they look great!

---

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

[andersonresende]

Thanks! I'll review it soon!