react-three-a11y
valtio
react-three-a11y | valtio | |
---|---|---|
7 | 47 | |
516 | 8,450 | |
1.6% | 1.4% | |
5.0 | 7.6 | |
3 months ago | 11 days ago | |
TypeScript | TypeScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
react-three-a11y
-
Show HN: 3D Framework for the Web. Built on Svelte and Three.js
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
-
how do you design scrolling "through" a website?
There is an accessibility library from drei: https://github.com/pmndrs/react-three-a11y
-
Making components Links (r3f/drei)
Caveat: Not the most accessible thing ever. The pmndrs crew made a tool that does this way more accessibly, this would be my production-grade recommendation: https://github.com/pmndrs/react-three-a11y
-
Is it even remotely practical to make Three.js experiences accessible? (controls/nav/text/objects/etc)
like /u/thesonglessbird said, it exists: https://github.com/pmndrs/react-three-a11y it covers screen readers, tabbing , focus indication, roles, and so on.
-
Chart.js 4.0 — new release of the popular open source charting library
That’s a bit of a cop out - React Three Fiber renders to a canvas too (obviously) and there’s a bunch of accessibility stuff in its semi-official ecosystem https://github.com/pmndrs/react-three-a11y
-
React Three Fiber and NextJS Starter Template
♿ R3F A11y
-
How to reproduce Death Stranding UI with react and react-three-fiber
To simulate the selected state you can try to use react-three-a11y. By wrapping our model with the component we will have access to hover, focus, and pressed state through useA11y() hook. We can try to display a SelectedMaterial based on the hover state for example.
valtio
- 5 Alternatives to Redux for React State Management
- How to properly structure a valtio shared state object?
-
Changelog #0023 — 🛠️ Internal refactoring and improvements
We took inspiration from the many frameworks we worked with throughout our careers. And maybe surprisingly, Django’s ORM layer impacted our design choices and the API quite a bit. The resulting framework relies on Zod for schemas and validation and Valtio for React integration.
-
Is redux and thunks still used or are there other alternatives for it now?
Valtio is like simplified MobX
-
Why is building a UI in Rust so hard?
Even simpler than Zustand are state-atom libraries like jotai or recoil, or proxy based ones like valtio. Here's some discussion about the differences.
-
How to implement state management inside a simple JavaScript app
There is a package developed around this proxy concept called Valtio which is available for JavaScript, React, and so on... feel free to check and star it on Github.
-
What is being used right now for ioc/state-managment?
I'm switching from redux-saga to valtio (https://github.com/pmndrs/valtio) for now. It's simple and easy to use, everything's great so far.
-
Ask HN: What is your favorite front end state management solution?
I like valtio, works w/ React or just js. Has subscribe, derive, and more.
https://github.com/pmndrs/valtio
-
Explanation on how Redux or React Context could help and picking the best option
Jotai and Valtio are both also really good. Recently looked at Nanostore as well and has some similarity to Jotai and Recoil.
-
Notes on LiveView Components and JS interactions
Since we want the React component to react to an external change, using a state manager makes this easy. We will use Valtio here by example. For this library, change the esbuild config to --target=es2020 instead to remove some warnings (for example, the Zustand library is ok).
What are some alternatives?
gltf-pipeline - Content pipeline tools for optimizing glTF assets. :globe_with_meridians:
redux - A JS library for predictable global state management
gltfjsx - 🎮 Turns GLTFs into JSX components
MobX - Simple, scalable state management.
react-three-fiber - 🇨🇭 A React renderer for Three.js [Moved to: https://github.com/pmndrs/react-three-fiber]
zustand - 🐻 Bear necessities for state management in React
awesome-react-three-fiber - 🍕 A loose collection of cool r3f links, gifs, people, stuff
Immer - Create the next immutable state by mutating the current one
r3f-experiments - Experiments with React Three Fiber
jotai - 👻 Primitive and flexible state management for React
leva - 🌋 React-first components GUI