threlte VS sites

Thanks! Threlte is "just" offering a declarative way to express Three.js. If you know how the `` component and its props and event handlers work, you can use the Three.js documentation for everything else.

Apart from that with Threlte I personally practice documentation-driven-development, so ecosystem packages are exhaustively documented. If you're missing something, let us know via an issue[1] or on Discord[2].

Accessibility is a topic we didn't care enough yet to be perfectly honest. Accessibility doesn't stop at screen readers though, it's about contrast, size, colors, motion, reachability, and so much more that we cannot provide and are a consumer topic. Naturally WebGL apps suffer from being practically invisible to screenreaders. There are workarounds[3] but essentially this has to be solved by consumers of Threlte (devs) and hopefully by browser vendors at some point in the future.

[1] https://github.com/threlte/threlte/issues

[2] http://chat.threlte.xyz

[3] https://github.com/pmndrs/react-three-a11y

more specifically it's using the svelte wrapper of three.js called Threlte: https://threlte.xyz/

Three.js is great when there is a layer between me and it's API. Been playing with https://threlte.xyz/ and really enjoying it.

Maybe try https://threlte.xyz/

Now this is a very high level overview and a lot of really important stuff is missing. Things like event propagation, pointermissed events, different event targets, a super clean syntax and more is all implemented in Threlte 6's interactivity plugin. Check out the code here.

GPT-4 is a fantastic tool for coding, really looking forward to using it with the latest Svelte docs. Perhaps consider adding the documentation for Threlte?

) with complex functionality, since the app needed a graphics pipeline and I wanted to write one up myself. The next page I made did not need a pipeline, so I opted to use Threlte (a Svelte version of react-three-fiber) to make the code simpler to write and easier to maintain. If a scene you want to create has a lot of different meshes, materials, animations, etc. you might be best off using Blender to get it looking perfect. You can export from Blender as .gltf files which can be imported into Three. If you want a more specialized solution, I'd need to know your use case a little better. How are you building the scenes?

Minor correction, svelte repl is in sites repo, and it's well maintained and updated.

I found this GitHub issue that feels relevant to the Svelte REPL issue. It sounds like unpkg doesn't successfully resolve the dependency due to differences between CJS and ESM.

You'd need to bundle the svelte compiler, then feed the compiled output of your string through a worker containing a browser build of rollup to bundle all of the internal dependencies. Have a look at https://github.com/sveltejs/sites/tree/master/packages/repl if you really want to go through with this.

See: https://github.com/sveltejs/sites/issues/113

Here's one built with Svelte: https://hn.svelte.dev/

It's not exactly an apples-to-apples comparison for a number of reasons including implementation and hosting differences, but might be interesting to people anyway. The code lives here: https://github.com/sveltejs/sites/tree/master/sites/hn.svelt...

Assuming you cloned https://github.com/sveltejs/sites, then you need to cd into sites/ (https://github.com/sveltejs/sites/tree/master/sites) and then into the site you want. Afterwards just follow the instructions in the README (usually pnpm i and pnpm run dev).

I'm pretty sure it's just your extension misbehaving. Here is the like to the repo: https://github.com/sveltejs/sites/tree/master/sites/svelte.dev

Hm, it works for me (iOS). Might be worth opening an issue on the site repo with the issue you’re seeing.

the kit.svelte.dev site is also fully open source, but it uses a lot of components which handle almost everything also uses api.svelte.dev, a non-svelte site to get all the data so I don't know how helpful that is either