Open sw-vish opened 9 months ago
We have a critical mass problem at the moment; the principal developer for all the recent work is focused on other projects at the moment. That large PR needs a lot more testing than I have done. If you have an app that could be ported to try this branch without too much difficulty, I'd be happy to help you with any questions about the dev workflow or even the API, since I've done a port recently. Just having someone new engaged in the project might be the catalyst we need.
Hi π
I wrote the big pr moving from reconciler to proxy this summer, but have been pre-occupied eversince. It's in a place where it needs actual codebases to be tested on, not the small tests I used when writing the code.
If you would like to test I recommend using Vorth's fork, he cleaned up some of the oddities in how I initially structured the repo.
Hi! Thanks for the replies.
I'm currently in the exploratory phases of a project with 3D requirements, which is how I came across this. I should be able to switch to using a different branch or fork without too much hassle, though given the early stage of the project it's unlikely to be a thorough test.
If I were to change branches, I have two questions:
You should use the fork, vorth/solid-three
, and the no-modules
branch there. You'll have to make a local clone of the fork, and also https://github.com/bigmistqke/drei
if you need it.
I have been testing successfully by using Yalc. See the commit message log and changes for commit 6e0ea83a88a1a8b008813a41ee0a10850534cc0b
. Yalc acts like a local npm repo, so you'll build and "publish" solid-three/fiber
first, then solid-three/drei
based on that (assuming you need it), then your own app. There is also a Yalc step that modifies a package.json
to use the Yalc repo... see the Yalc docs.
To spell this out a little more clearly: (don't assume these are ready-to-use command lines!)
Thanks for the detailed instructions!
I was able to clone and build vorth/solid-three
(no-modules
branch), though I did get some Typescript errors (log below), and then add it using yalc
. Migration was relatively straightforward, mostly involving updating the import declarations and changing JSX element names. The most prominent issues so far are:
<T.Primitive />
to show a loaded model, I can set the rotation
property and it works correctly, but is flagged by TSC as not existing on the element.<T.Primitive />
also doesn't seem to handle any click/pointer events. I added onClick={x => console.log(x)}
but nothing happens.It's possible that I'm not using these elements correctly, or have missed a configuration, or they're just a result of the build errors.
I haven't used solid-drei
thus far, since it isn't published. I've instead just been replicating the elements I need (eg. Controls). I did clone it and try to build the solid-drei
branch but got stymied by a ton of Typescript errors.
Hi, I've been looking into using Three.JS with SolidJs and found this package. However, the last release on NPM was 8 months ago. Looking around, I can see there's a large pull request as well as recently updated fork at https://github.com/vorth/solid-three. So, I'm wondering if there are any plans to release a new version to NPM any time soon?
Thanks!