
Brisa 0.2.7
by Aral Roca
This release introduces new features, bug fixes, and documentation improvements to enhance the Brisa experience. Let’s dive into what's new!
✨ New Features
peek()
If you want to get the value of a signal without subscribing to an effect, you can use the peek
method:
const count = state<number>(0);
const addition = state<number>(1);
effect(() => {
count.value = count.peek() + addition.peek();
});
In this example, the count
state will be updated only when the addition
state changes.
- Signals:
peek()
Method – Addedpeek()
to signals, allowing you to read the value without tracking dependencies. Also, improved documentation forstore.Map
. – @aralroca in #752
🐞 Bug Fixes
- Server Actions: Now only imports valid identifiers, preventing unintended issues. – @aralroca in #757
- Type Safety in i18n: Improved type safety when returning objects in i18n. – @aralroca in #762
- i18n &
notFound()
Handling: Ensured i18n correctly resolves after callingnotFound()
. – @aralroca in #764
📖 Documentation & Examples Updates
- Reactivity Docs: Enhanced documentation for Brisa’s reactivity system and types. – @aralroca in #753
- Web Context Docs: Improved clarity and structure in web context documentation. – @aralroca in #760
- New Example: Added a WebSocket chat example to showcase real-time communication. – @aralroca in #755
- Docs Fixes: Fixed minor variable issues and improved consistency. – @aralroca in #759
🔄 Maintenance
Full Changelog
🔗 https://github.com/brisa-build/brisa/compare/0.2.6...0.2.7
❤️ Support Brisa: Visit our shop for Brisa swag! 🛍️