[Frontend] Align Next.js and eslint-config-next major versions

Open Beginner friendly
#830 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
eslint, next.js, typescript
Domain
frontend, tooling

Research direction

Start with package.json on the latest main branch and inspect the Next.js and eslint-config-next versions and available scripts. Align the major versions, document the supported version matrix, and verify lint, type-check, test, and production-build commands. Done means the compatibility issue is addressed and the required checks pass without unrelated changes.

Written by the indexing model from the issue text.

Description

enhancement frontend help wanted

Problem

The app uses Next 16 while eslint-config-next remains on 15.2.0, risking incompatible rules and parser behavior.

Relevant code

package.json

Proposed scope

Upgrade to compatible versions, document the supported matrix, and verify lint, type-check, test, and production build.

Acceptance criteria

  • The reported behavior is reproduced or characterized with a focused automated test before the fix.
  • The implementation satisfies the proposed scope without weakening TypeScript, lint, authorization, privacy, or error handling.
  • Success, empty/loading where applicable, failure, and boundary cases are covered.
  • Existing related tests pass and new regression coverage is included.
  • User-facing behavior remains accessible by keyboard and at mobile viewport sizes where UI is affected.
  • Documentation is updated when the change alters configuration, contracts, security assumptions, or contributor workflow.

Contributor notes

Base the work on the latest main branch. Keep unrelated refactors out of the pull request and include screenshots or recordings for visible changes. Never use real pet, medical, contact, wallet, or credential data in fixtures.

Dominant language
TypeScript
Stars
3
Forks
159
Avg merge
3d 6h
Merged PRs (30d)
36

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DogStark/petChain-Frontend

All issues in DogStark/petChain-Frontend

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.