facebookexperimental/Recoil

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

Open

#1570 opened on Jan 27, 2022

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

Description

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

Contributor guide

Tech stack
javascriptreactnextjs
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
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.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
ReactNextJSRecoil basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the duplicate atom key error in Recoil when used with NextJS SSR. The issue description lacks details; check the comments for reproduction steps. Look into Recoil's atom key generation and how it handles server side rendering. Relevant files may include packages/recoil/recoil values/Recoil Atom.js and related NextJS configuration. The root cause is likely due to multiple instances of Recoil root or incorrect key uniqueness across server and client.