Kieran Mann

@mattphillips I'm interested in helping out, I'll take a look at the code this weekend. I think supporting member methods would widen the appeal of this plugin quite a bit...

Not planning on pursuing this personally in favor of VS Code's debug mode.

Keen to hear your thoughts on typing `OffscreenCanvas` @joshuaellis (thanks for taking over the three.js typings btw)

FYI The folks over at Poimandres seem to have forked this lib for `@react-three/fiber`'s purposes and implemented this feature along with a few others: https://github.com/pmndrs/use-asset#hooks-and-global-cache

Seems ByteStream exists in the `index.d.ts` but I have a slightly different but related problem: https://codesandbox.io/s/typescript-forked-ei38tw?file=/src/index.ts TypeScript complains if you try to construct one since it's exported as an interface...

+1 on this, was rather surprised to get an object containing the full DataSet as UInt8Array logged in an error handler. Happy to help if version 2.0 is planned.

For app code working with buffer geometries, it would also be nice to go a bit further and narrow the specific attributes that are defined as well as their respective...

Submitted a proposed approach, will wait for a signal: https://github.com/three-types/three-ts-types/pull/241

Would this be required to use it with ShareDB on the server? Trying to understand how this fits in with `WebSocketJSONStream`. Client API makes sense but I don't get how...

Figured it out. My issue was actually #101 For future readers (if the interface hasn't been fixed in the library), to work with ShareDB on the server, the following did...