Esta semana sacamos nuestro último videoclip. Os presentamos la historia tras 'Todas aquellas luces', junto con nuestros hermanos de @paraleia!
https://t.co/sY7YnKfHGd
I was replacing Vitepress with Brisa for the Brisa documentation and realized that no WC exists to search similar to Vitepress 🤔
🎉 Now there is, inspired by Vitepress, and can be used in any framework (React, Brisa, Vue, Svelte, Solid.js, Qwik) or Vanilla.js 👇
📙 https://t.co/SZ7bxku3j9
🔗 https://t.co/E1h0kVk5r4
For React fans, Brisa is written with JSX for both server and web components, very similar.
For fans of Next.js, Brisa is based on filesystem router, including web components, also 0 config.
For Preact fans, Brisa together with the signals occupies 3kb, very inspired by Preact.
For Solidjs fans, Brisa is based on JSX and signals, with build-time optimizations to make it easy to consume props, set defaults, and destructuring without losing reactivity.
For Tauri fans, Brisa is fully integrated with Tauri, you can transform your web app to android, ios or desktop app with a single property configuration.
For people who are fans of web components, Brisa makes SSR of web components working with signals and written with JSX and optimized for low kb growth.
For HTMX fans, in Brisa you can make a SPA without any web component and all with Brisa RPC (2kb) and server actions (server actions concept different from React).
For Qwik fans, I started creating Brisa when @mhevery came to Barcelona and talked about Qwik as if it was his baby, his motivation motivated me to start putting my ideas into a framework.
For Vue fans, my co-worker @notphanan from the Vue core, gave me a lot of support to get started with Brisa. All the current documentation is in Vitepress and has allowed us to go fast. However, when we migrate it to Brisapress we will be heavily inspired to Vitepress.
I want to thank all the frameworks that exist and the great community that exists. Brisa has taken very good ideas from many of them and without them Brisa would not have been possible.
If you want to know more, it will soon be public -> https://t.co/dzGHOGrjhF 💪
This video was passed to me by @danielofair, who is helping me with the documentation in Brisa 📖
Very grateful to all the people who already want to contribute without being public yet ❤️
If you also want to contribute to Brisa, write me privately. There are still some months to go before the beta is open 😊
Brisa introduces two new concepts of Server Actions:
▶ Server Events:
Server actions can be passed through props on both server components and web components.
It can be used beyond the form element, in all browser events. As long as the event is captured within the web component it is a normal browser event, the moment the event goes up to the server component level the RPC makes the request to execute the action on the server. The server components are pure HTML elements and have as an attribute the ID of the correct action even if it has been passed from another server component, that is why they look like server events.
▶ Action Signal:
Server components have a store that lives only during the request, they are never saved. But what can be done is to transfer fields from the store with the client, and then the action has it again, it can be modified and the web components that consume the store via signal react to the changes.
▶ TLDR; The idea is to run server code in server components and browser code in web components and improve the communication between both worlds without the need to "use client" and "use server".
Brisa is still experimental, I estimate that this summer I will open it open-source for the whole world.
Música para todos. Únete en
@NAS_Spotlight#spotify#playlists
https://t.co/oxkzmYjUPL
https://t.co/PIQCbXFDnV
https://t.co/Aqzm3xJgLH
https://t.co/fxssKliO7k
https://t.co/2W050RZ8Ue
https://t.co/ZJcn531PuO
https://t.co/bKYBMgiF9u
@edeagle89#iwantmynas#stoppayola