You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: We're currently in the process of adding in the sub-issues!
The CodeMirror v6 upgrade has been in development over the past few years with many major contributions from folks within the community. Over the past few months @khanniie leading the final push to wrap-up this project! At this stage, we're currently looking for testing, feedback, and support to address remaining issues, which we'll be tracking as sub-issues.
If you'd like to contribute, please work off of thedevelop-codemirror-v6 branch, which is dedicated to this feature. Please note that this is separate from the maindevelop branch.
I also included a link to a Release testing environment built from the develop-codemirror-v6 branch. While I recommend running the branch locally during your development process, feel free to use this as reference!
Please feel free to explore the work so far, check out the sub-issues, or let us know if you have any questions about setting up or working with the branch!
Thanks for your interest in these issues @avinxshKD and @Jatin24062005! We're in the process of opening up a few more this week, so please be on the lookout once they've been added!
I've been exploring the develop-codemirror-v6 branch and have a working implementation in progress. Here's my approach:
Extracting p5 identifiers from the existing p5Hinter list (already categorized by type: method, constant, variable).
Using a CM6 ViewPlugin with RangeSetBuilder to efficiently decorate only the visible viewport.
Applying separate decoration classes (cm-p5-method, cm-p5-constant, cm-p5-variable) so each type gets distinct highlighting.
Hooking into the existing _editor.scss theme system via getThemifyVariable() so all themes (light, dark, high contrast) are supported automatically.
The plugin is conditionally registered only for JavaScript files in createNewFileState, keeping it scoped correctly.
Currently testing locally. Will open a PR on the develop-codemirror-v6 branch shortly.
Activity
tidier.js#3816avinxshKD commentedon Jan 28, 2026
hey @raclim I'd like to work on this, pls assign it to me? thanks
Jatin24062005 commentedon Jan 30, 2026
@raclim can i take these enhancements ?
raclim commentedon Feb 3, 2026
Thanks for your interest in these issues @avinxshKD and @Jatin24062005! We're in the process of opening up a few more this week, so please be on the lookout once they've been added!
stateUtils.js#38692 remaining items
ravuri-nikhil commentedon Feb 20, 2026
Hi @raclim are these issues open to work?
rishabhk119 commentedon Mar 22, 2026
Hi @raclim, I'd like to work on this issue.
I've been exploring the develop-codemirror-v6 branch and have a working implementation in progress. Here's my approach:
Extracting p5 identifiers from the existing p5Hinter list (already categorized by type: method, constant, variable).
Using a CM6 ViewPlugin with RangeSetBuilder to efficiently decorate only the visible viewport.
Applying separate decoration classes (cm-p5-method, cm-p5-constant, cm-p5-variable) so each type gets distinct highlighting.
Hooking into the existing _editor.scss theme system via getThemifyVariable() so all themes (light, dark, high contrast) are supported automatically.
The plugin is conditionally registered only for JavaScript files in createNewFileState, keeping it scoped correctly.
Currently testing locally. Will open a PR on the develop-codemirror-v6 branch shortly.