OriginProtocol / OriginProtocol/origin-dollar
Next.js fast refresh breaks reactivity of pullstate
Open
Nobody has claimed this yet.
- Dominant language
- Solidity
- Stars
- 152
- Forks
- 115
- Avg merge
- 3d 20h
- Merged PRs (30d)
- 17
Description
I couldn't figure out why my components weren't updating on store changes, but turns out the subject is the reason.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked Next.js issue 13268, which is the only investigation reference provided. The report names Fast Refresh, reactivity, and pullstate but does not identify a repository file, test, requested change, or completion condition, so the next step and definition of done remain unresolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- next.js
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100