processing / processing/p5.js

[p5.js 2.0+ Bug Report]: p5js editor gives wrong (spurious) line number for errors

Open
#8,942 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area:Utilities p5.js 2.0+
Dominant language
JavaScript
Stars
24k
Forks
3.8k
Avg merge
3d 16h
Merged PRs (30d)
25

Description

Most appropriate sub-area of p5.js?
  • Accessibility
  • Color
  • Core/Environment/Rendering
  • Data
  • DOM
  • Events
  • Image
  • IO
  • Math
  • Typography
  • Utilities
  • WebGL
  • WebGPU
  • p5.strands
  • Build process
  • Unit testing
  • Internationalization
  • Friendly errors
  • Other (specify if possible)
p5.js version

2.2.3

Web browser and version

Firefox 151.0.4

Operating system

MacOS 26.5.1

Steps to reproduce this

Line numbers associated with any errors are no where near the actual error which makes debugging difficult.

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

Start by reproducing the incorrect error location in the p5.js editor using p5.js 2.2.3, Firefox 151.0.4, and the supplied macOS version. Compare the reported line with the actual failing line; done means editor errors consistently identify the correct line.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.