Vapor Chamber - A lightweight command bus designed for Vue Vapor. ~1KB core. #14373
Replies: 4 comments
-
|
Working with Vue reactivity system and compilers can sometimes present interesting edge cases. A few quick things to consider regarding this topic:
I highly recommend checking out the Vue DevTools extension to inspect the component tree and verify if the state is updating as expected. Let me know if you want to dig deeper into the specific component logic. Hope this points you in the right direction! Let me know how it goes. Happy coding! |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @aniruddhaadak80 for the sharp observations on Vue’s reactivity model, especially around proxy trap behavior and the risks of accessing internal runtime properties. Your points directly informed several fixes in this release - from correcting signal usage and v-model bindings to removing the window.VUE_VAPOR probe and tightening lifecycle cleanup. The full changelog is now updated with all related improvements. Greatly appreciate the depth of your feedback. |
Beta Was this translation helpful? Give feedback.
-
|
v0.40 - Vue 3.6 + Vite 7/8 Alignment Pre-release This release aligns vapor-chamber with the Vue 3.6 beta (Vapor mode feature-complete) |
Beta Was this translation helpful? Give feedback.
-
|
🚀 vapor-chamber v1.0.0 is officially live! I’m excited to share that vapor-chamber has reached its first stable release. After testing and refining, version 1.0.0 is now available on npm. What’s new in 1.0:
Check it out here: https://www.npmjs.com/package/vapor-chamber Thanks to everyone for the feedback during the 0.x phase! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Built something I think fits nicely with the direction Vue Vapor is heading. Vapor Chamber is a tiny (~1KB) command bus designed specifically for Vapor’s signal‑driven model. Instead of scattering emits/listeners across components, it gives you a single, semantic place to handle actions — with a plugin pipeline for logging, validation, history/undo, debounce/throttle, etc.
If you’re experimenting with Vapor and want a minimal, predictable way to structure app logic without the VDOM overhead, I’d love feedback.
npm install vapor-chamber
https://github.com/lucianofedericopereira/vapor-chamber
Feedback appreciated — especially from anyone already experimenting with Vapor.
Beta Was this translation helpful? Give feedback.
All reactions