Gianmarco

TODO Fix glslify in examples so that we don't have to copypaste in .js files

4

Should be easy to use the glslify babel macro

Default vert would be used like ``` // empty ``` and result in a default non-transforming vertex shader ```glsl void main() { gl_Position = projectionMatrix * modelViewMatrix * vec4(position,1.); }...

We started the project including babel-glsl-macro in the library to let users just add glslify-type imports that would just work. We later removed it because we didn't want to make...

ShaderMaterial and RawShaderMaterial don't use chunks, so you can just use strings and a simpler tree like this ```jsx {/* common would be added to both vert and frag */}...

Dark mode

3

Because of course

feat: react 18

4

Depends on - #329 ### TODO - [ ] Use zustand 4 release candidate

ci: moves to pnpm

3

- Takes the pnpmfile.cjs thing from #276 - Removes Cypress as we aren't really using - Moves to pnpm as yarn 3 never felt good - adds manypkg to lint...

### How do we make creating plugins easier? I think we should consider having an abstract class for plugins to aid with typing ```js class NumberPlugin extends LevaPlugin { name:...

Serialization & persistance

6

Users should be able to persist changes or to serialize and saved them @emmelleppi started doing work for this in use-tweaks I think this one will be way easier since...

This would be an opt-in via component.