reactjs / reactjs/react.dev

[Bug]: Unhandled Runtime Error(RangeError) while running on my local server

Open
#7,947 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug: unconfirmed
Dominant language
JavaScript
Stars
11.8k
Forks
7.9k
Avg merge
1d 11h
Merged PRs (30d)
11

Description

Summary

When i was reading the docs on my local server, and doing the exercises in the editor, an error occurred.

Unhandled Runtime Error

RangeError: Position 115 is out of range for changeset of length 114

ignore frames

mapPos
node_modules/@codemirror/state/dist/index.js (801:1)
findSharedChunks
node_modules/@codemirror/state/dist/index.js (3519:1)
compare
node_modules/@codemirror/state/dist/index.js (3313:1)
findChangedDeco
node_modules/@codemirror/view/dist/index.js (3053:13)
update
node_modules/@codemirror/view/dist/index.js (2585:1)
update
node_modules/@codemirror/view/dist/index.js (6557:1)
flush
node_modules/@codemirror/view/dist/index.js (6261:1)
forceFlush
node_modules/@codemirror/view/dist/index.js (6206:1)
measure
node_modules/@codemirror/view/dist/index.js (6660:1)
requestMeasure/this.measureScheduled<
node_modules/@codemirror/view/dist/index.js (6811:1)

Page

react.dev(running on my localhost)

Details

No response

Contributor guide

Open the contributing guide

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.

Research direction

Reproduce the error while reading react.dev locally and using an exercise in the editor. Start with the reported @codemirror/state mapPos and @codemirror/view update stack frames, then trace the react.dev editor integration around that update. Done means the exercise editor runs without the RangeError.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
documentation, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.