`three-bmfont-text` dependency breaks with Deno, please remove it
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- Half a day
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- deno, javascript, node.js
- Domain
- build-system
Research direction
The failing dependency is the github:dmarcos/three-bmfont-text entry that [email protected] pulls in, so start with package.json and check where three-bmfont-text is imported in the source, likely the text component. Look for an npm-published release that provides the same API, and confirm the choice with maintainers before swapping it. Done means the package resolves from npm, Deno installs it, and the existing text tests still pass.
Written by the indexing model from the issue text.
Description
Even though this has been reported as part of several existing issues (like #4564, #4329), these won't mention the problem that this (GitHub resolved) dependency creates:
error: Error in [email protected] parsing version requirement for dependency "three-bmfont-text": "github:dmarcos/three-bmfont-text#c3eec235b9188aa0d8ed949101236e6d5fccf071"
Caused by:
Package specified a dependency outside of npm (github:dmarcos/three-bmfont-text#c3eec235b9188aa0d8ed949101236e6d5fccf071). Deno does not install these for security reasons. The npm package should be improved to have all its dependencies on npm.
To work around this, you can use a package.json and install the dependencies via `npm install`.
Error: Process completed with exit code 1.
- Dominant language
- JavaScript
- Stars
- 17.7k
- Forks
- 4.4k
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from aframevr/aframe
-
Removing grabbable does not remove obb-colliderPossibly taken @mrxz claimed this 28 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Uncaught TypeError: Cannot read properties of null (reading 'cancelAnimationFrame') on session endOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Quest WebXR: tracked-controls reports false controller disconnects when a Touch source moves to trackedSourcesPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 65/100
-
TypeError: session.requestAnimationFrame is not a function when re-entering XR session after exitOpen
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
tracked-controls-webxr does not update entity position when referenceSpaceType is bounded-floorOpen
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Similar issues
-
bug needs triage P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
pbakaus/impeccable#1143 ·
Maintainers usually reply within 1 day
-
status: waiting for maintainer
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
mui/material-ui#49547 ·
Maintainers usually reply within 1 day
-
next() is called twice when the request closes after busboy fails to startPossibly taken @NgoQuocViet2001 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
[2.x] extension-manager: translation keys that changed meaning keep their old namesPossibly taken A pull request linked to this issue is open or already merged. Opentype/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day