pmndrs / pmndrs/examples

problematic demos

Open
#38 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
122
Forks
29
Avg merge
3d 12h
Merged PRs (30d)
2

Description

Excluding "minor" coloring/lightning/tonmapping issues https://github.com/pmndrs/examples/issues/11

Here are the "problematic" demos that:

does not build

Some demos/* have been temporarily disabled (renamed "bbuild2" with 2 "b" instead of "build2" like others one) because of build errors.

For them, please test with:

$ npm run -w demos/bvh bbuild2
$ # if succeeded, renane `demos/bvh/package.json#scripts.bbuild2` into `build2`

is blank or error(s) in console

$ npm run -w demos/basic-ballpit dev

something is broken compared to original

Contributor guide

No contributing guide indexed for this repository

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 with the unchecked demos listed in the issue, using the provided npm commands: run the relevant bbuild2 script for build failures and npm run -w demos/ dev for blank or console-error cases. Compare the affected demos with their original behavior where noted. Done means each targeted demo builds, runs without the reported errors, or matches the stated original behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
build-system, frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
40/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.