facebookexperimental/Recoil

[SSR][NextJS] Duplicate atom key during development and during production build in nextjs

Open

#1,570 opened on Jan 27, 2022

View on GitHub
 (3 comments) (2 reactions) (0 assignees)JavaScript (1,151 forks)batch import
help wantedserver rendering

Repository metrics

Stars
 (19,428 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

I have problems in production as it gives an internal server error.

Contributor guide

Research direction
Investigate the duplicate atom key issue in Next.js SSR and production builds. Trace the atom key generation logic and ensure uniqueness across server and client renders.
Tech stack
reactnextjsjavascript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
ReactNext.jsRecoil
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50