Skip to content

Proposal: Official CLI for a smoother transition from Web Editor to local development #9107

Description

@Danyccsf

Increasing access

An official CLI would lower the barrier for beginners transitioning from the Web Editor to local development. Currently, the setup friction of managing local files, folder structures, and dependencies can be a major "drop-off" point for new coders. By providing a standardized tool, we make local development more approachable and consistent for all users, regardless of their technical background.

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)

Feature request details

I propose an official, lightweight p5.js CLI tool to provide a unified path from the Web Editor to local development.

Key Features:

  • Project Scaffolding: Instantly generate a project folder with a local copy of p5.js, a ready-to-run index.html, sketch.js, and style.css.

  • Sensible Defaults: Templates that mirror Web Editor behavior for canvas sizing and DOM organization to ensure sketches "just work" when moved locally.

  • Editor Agnostic: Works in any terminal, allowing users to choose their own IDE (VS Code, Sublime, Vim, etc.) without losing the simplicity of the p5.js environment.

Implementation Strategy:
The project could begin by auditing the existing VS Code Project Generator and other community tools to identify the most useful functionality. A lightweight Node.js scaffolding tool could then be developed to generate structures and manage the local p5.js dependency.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions