processing/p5.js

[p5.js 2.0 Bug Report]: Warnings about omitting strokes on high-detail 3D primitives don't use FES

Open

#8387 opened on Jan 7, 2026

View on GitHub
 (16 comments) (0 reactions) (1 assignee)JavaScript (20,784 stars) (3,178 forks)batch import
Area:WebGLGood First IssueHelp Wantedp5.js 2.0+

Description

Most appropriate sub-area of p5.js?

  • Accessibility
  • Color
  • Core/Environment/Rendering
  • Data
  • DOM
  • Events
  • Image
  • IO
  • Math
  • Typography
  • Utilities
  • WebGL
  • Build process
  • Unit testing
  • Internationalization
  • Friendly errors
  • Other (specify if possible)

p5.js version

All

Web browser and version

All

Operating system

All

Steps to reproduce this

Steps:

  1. Turn off FES
  2. Draw a cylinder with a high level of detail
  3. It still logs a warning

That's because these sorts of warnings are raw console.logs in the codebase: https://github.com/processing/p5.js/blob/9799eada451dea7f2b50fe5f52ffd725463b343a/src/webgl/3d_primitives.js#L2582-L2585

Snippet:

p5.disableFriendlyErrors = true
function setup() {
  createCanvas(400, 400, WEBGL);
  cylinder(20, 100, 40, 40)
}

Additionally, this also triggers when you are drawing to a p5.Geometry, i.e.:

function setup() {
  createCanvas(400, 400, WEBGL);
  const myGeom = buildGeometry(() => cylinder(20, 100, 40, 40))
  noStroke()
  model(geom)
}

Arguably we should just silence this error if inside of buildGeometry since we don't know if it will eventually be drawn with strokes or not, to avoid misleading false positives.

Contributor guide

Tech stack
javascript
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptp5.jsFriendly Error System
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Investigate the use of Friendly Error System (FES) in p5.js, particularly in other areas where console.warn or console.log are replaced. The specific lines to modify are in src/webgl/3d primitives.js around line 2582. Consider the edge case of buildGeometry() where the warning should be suppressed to avoid false positives. Review existing FES functions like p5. friendlyError or similar. Test that p5.disableFriendlyErrors = true suppresses the warning after the fix.