max-mapper / max-mapper/requirebin

Debug mode

Open
#121 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
389
Forks
73
PR merge metrics
No merged PRs in 30d

Description

requirebin seems to use browserify without --debug, it would be nice if requirebin turned debug mode on.

Example using regl (working requirebin):


const quad = require('glsl-quad');
const regl = require('regl')();

let frag = `
    THIS IS AN OBVIOUSLY BAD SHADER.

  IT SHOULD THROW AN ERROR.

  BUT REGL ONLY THROWS AN ERROR IN DEBUG MODE.

  WHICH MEANS WE WILL ONLY SEE A WARNING. (CHECK
  THE CONSOLE).

             CAN WE GET REQUIREBIN
              TO USE DEBUG MODE?
`;

let draw = regl({
  vert: quad.shader.vert,
  frag: frag,
  attributes: {
    a_position: quad.verts,
    a_uv: quad.uvs
  },
  elements: quad.indices,
  uniforms: {
    u_clip_y: 1
  }
});

draw();

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

The issue identifies requirebin's Browserify invocation but names no file or test. Locate where Browserify is configured, check how its debug option is passed, and use the linked regl example to verify that the shader failure produces the expected debug error rather than only a warning.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
tooling, web-dev
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.