Example assets get 404 errors for 'loader' base64 examples
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 40.3k
- Forks
- 7.2k
- PR merge metrics
- No merged PRs in 30d
Description
The assets required for most of the base64 loader examples are 404'ing:
Assets are embedded with URLs like:
https://phaserexamples.com/assets/base64/spooky-atlas.js
The files themselves still exist in the Examples repo:
https://github.com/phaserjs/examples/blob/master/public/assets/base64/spooky-atlas.js
Observed for:
https://phaser.io/examples/v3.85.0/loader/base64/view/base64-texture-atlas
https://phaser.io/examples/v3.85.0/loader/base64/view/base64-image
https://phaser.io/examples/v3.85.0/loader/base64/view/base64-bitmap-font
https://phaser.io/examples/v3.85.0/loader/base64/view/base64-texture-atlas
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the affected base64 loader examples and compare their asset URLs with the files in the Examples repository, especially public/assets/base64/spooky-atlas.js. Check the listed example pages for the 404 responses; done means the referenced base64 assets load successfully for the affected examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100