ThreeJs has an abstraction that allows you to write your shaders using JavaScript, it is called ThreeJS Shading Language. This implementation makes of that to simplify development:
https://github.com/mrdoob/three.js/wiki/Three.js-Shading-Lan...
In Three-LLM: Three.js-based WebGPU LLM inference enginemrdoob
three.js
JavaScript2010–2026
mrdoob / three.js
three.js
JavaScript 3D Library.
79Distinct people
97Mentions
0Explicit recommenders
118.3KGitHub stars
What to know before exploring
What it is
JavaScript 3D Library.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- fairfieldt/xcjs · linked in 2 of the same discussions
- lostdecade/diggy · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year97 dated mentions
Observed mentions: 2010-04-25 21:11:46 UTC to 2026-09-03 20:55:40 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2010 | 2010-01-01 00:00:00 UTC | 2011-01-01 00:00:00 UTC | 9 | 3 | 6 |
| 2011 | 2011-01-01 00:00:00 UTC | 2012-01-01 00:00:00 UTC | 12 | 2 | 10 |
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 8 | 3 | 5 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 8 | 2 | 6 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 6 | 0 | 6 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 7 | 2 | 5 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 10 | 2 | 8 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 9 | 0 | 9 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 5 | 0 | 5 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 3 | 3 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 5 | 1 | 4 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 3 | 0 | 3 |
From the project README
An excerpt from the repository, fetched Nov 13, 2026.
Read the project’s introduction
three.js
JavaScript 3D library
The aim of the project is to create an easy-to-use, lightweight, cross-browser, general-purpose 3D library. The current builds only include WebGL and WebGPU renderers but SVG and CSS3D renderers are also available as addons.
Examples —
Docs —
Manual —
Wiki —
Migrating —
Questions —
Forum —
Discord
Usage
This code creates a scene, a camera, and a geometric cube, and it adds the cube to the scene. It then creates a WebGL renderer for the scene and camera, and it adds that viewport to the document.body element. Finally, it animates the cube within the scene for the camera.
import * as THREE from 'three';
const width = window.innerWidth, height = window.innerHeight;
// init
const camera = new THREE.PerspectiveCamera( 70, width / height, 0.01, 10 );
camera.position.z = 1;
const scene = new THREE.Scene();
const geometry = new THREE.BoxGeometry( 0.2, 0.2, 0.2 );
const material = new THREE.MeshNormalMaterial();
const mesh = new THREE.Mesh( geometry, material );
scene.add( mesh );
const renderer = new THREE.WebGLRenderer( { antialias: true } );
renderer.setSize( width, height );
renderer.setAnimationLoop( animate );
document.body.appendChild( renderer.domElement );
// animation
function animate( time ) {
mesh.rotation.x = time / 2000;
mesh.rotation.y = time / 1000;
renderer.render( scene, camera );
}
If everything goes well, you should see this.
Cloning this repository
Cloning the repo with all its history results in a ~2 GB download. If you don't need the whole history you can use the depth parameter to significantly reduce download size.
git clone --depth=1 https://github.com/mrdoob/three.js.git
Change log
Releases
Read the full README on GitHubWhat Hacker News says
97 sourcesNo, it's using the newish SSGI and TRAA webgpu nodes. The three team has been making great progress with SSGI and webgpu in general and i'd recommend checking it out if you're interested.
There's also a denoise node in three (not used in this example), but SSGI still looks kinda blurry.
Work though is still going on:
https://github.com/mrdoob/three.js/issues/31892
In Ball PitXUASTC was just released, allowing for all ASTC Block sizes to be used on the web, once support lands in the big web 3D libraries like Three.js [1].
To me, this is huge. Relying on pre-calculated lighting when building stuff like [2], I constantly fight for VRAM, as older iPhones have very strict limits. XUASTC brings the all the remaining modern GPU compression schemes to the web in a standardized manner.
[1] https://github.com/mrdoob/three.js
[2] https://mymachine.dmgmori.com/
In Basis Universal v2conradev found likely the right version of the file here: https://github.com/mrdoob/three.js/blob/55b4bbb7ef7e29b214b9...
In Codex, Opus, Gemini try to build Counter StrikeIt's taken from a threejs example: https://github.com/mrdoob/three.js/blob/dev/examples/jsm/obj...
Seems fine given the project is already using threejs and so will have to include license info for it already.
In Codex, Opus, Gemini try to build Counter StrikeI believe it is MIT-licensed code from three.js: https://github.com/mrdoob/three.js/blob/55b4bbb7ef7e29b214b9...
In Codex, Opus, Gemini try to build Counter StrikeVisualizing data with 3D flowers in Vue and Three.js
2 points · Open discussionUnfortunate - they didn't pin the version of Three.js they were using for the interactive viewer at https://www.math.uwaterloo.ca/tsp/star/star10m_tour.html
And as a result it's been broken since May 2022: https://github.com/mrdoob/three.js/releases/tag/r141
I downloaded the HTML file and replaced the link with a versioned one, and the viewer still works just fine.
In Shortest-possible walking tour to 81,998 bars in South KoreaMaking the world better commit by commit
3 points · Open discussionI'm a graphics programmer who has quite a bit of experience with WebGL, and (disclaimer) I've also contributed to the WebGPU spec.
> Quite honestly, I have no idea how ThreeJS manages to be so robust, but it does manage somehow.
> To be clear, me not being able to internalize WebGL is probably a shortcoming of my own. People smarter than me have been able to build amazing stuff with WebGL (and OpenGL outside the web), but it just never really clicked for me.
WebGL (and OpenGL) are awful APIs that can give you a very backwards impression about how to use them, and are very state-sensitive. It is not your fault for getting stuck here. Basically one of the first things everybody does is build a sane layer on top of OpenGL; if you are using gl.enable(gl.BLEND) in your core render loop, you have basically already failed.
The first thing everyb
Read the rest
ody does when they start working with WebGL is basically build a little helper on top that makes it easier to control its state logic and do draws all in one go. You can find this helper in three.js here: https://github.com/mrdoob/three.js/blob/master/src/renderers...
> Luckily, accessing an array is safe-guarded by an implicit clamp, so every write past the end of the array will end up writing to the last element of the array
This article might be a bit out of date (mind putting a publish date on these articles?), but these days, the language has been a bit relaxed. From https://gpuweb.github.io/gpuweb/#security-shader :
> If the shader attempts to write data outside of physical resource bounds, the implementation is allowed to:
> * write the value to a different location within the resource bounds
> * discard the write operation
> * partially discard the draw or dispatch call
The rest seems accurate.
Fun fact, a lot of it is open source, just not where you would expect it. During the creation of Clara.io I created over 200 PRs to Three.js:
https://github.com/mrdoob/three.js/pulls?q=is%3Apr+author%3A...
Open sourcing it wholesale at this point is a challenge because parts of the tech stack became parts of Threekit.com. Threekit.com is VC funded and an ongoing business operation.
I do what I can with open source still, see:
https://github.com/bhouston/behave-graph
https://github.com/threeify/threeify
In Clara.io Shutting DownNothing to add on Clara.io. However, just wanted to state that Ben Houston is/was one of the more prolific three.js contributors (https://github.com/mrdoob/three.js/graphs/contributors) and consistently pushed three.js in a better direction. Thank you!
In Clara.io Shutting DownIt's using Three.js[^1] with Photons[^2], and a number of other interesting libraries for calculation like satellite-js[^3].
[1]: https://github.com/mrdoob/three.js/
[2]: https://github.com/mkkellogg/Photons
[3]: https://github.com/shashwatak/satellite-js
In Low Earth Orbit VisualizationShowing the 15 most recent of 97 sources. Enable JavaScript to search and browse every indexed mention.