brisa

Already added to the route-map. I share it here in case you want to add more proposals: https://github.com/brisa-build/brisa/issues/197

If you have JavaScript disabled, the onSubmit still works, the rest of the events do not, similar to other frameworks, this is because of the nature of the form and JS. If there are proposals on how to improve this, we are open to you to write them on GitHub and we will take them into account: https://github.com/brisa-build/brisa

It's a POST request. Try this example and inspect the Network: https://github.com/brisa-build/brisa/tree/main/examples/with... In build-time, each server action is converted to an API entry point.

The only cache is via "Cache-Control". By default is this one: https://github.com/brisa-build/brisa/blob/2e14f765f425c129a6... However, is possible to change any response header including this one: https://brisa.build/building-your-application/routing/pages-... Other than this. We don't like to use cache, because a framework needing cache is a sign of a patch to cover a problem. We are fast by nature, we invite you to try it and you will see that the server takes 4-5ms to render. However, an important part for the 1.0 routing is to do a lot of optimizations that we already have in mind.

We are not using a Proxy, the implementation of the signals is as follows: https://github.com/brisa-build/brisa/blob/main/packages/bris... By rule, reactivity is broken if you declare a variable using the getter (.value) outside the JSX. This is because the component is called once, and during the rendering of the DOM elements, effect wrappers are added to register the getters (.value) of any signals. However, to make life easier for developers, we make some optimizations in build time, to: 1. Support early returns. 2. Not having to use .value in the props (well, “WC attributes”) and being able to define default values, do destructuring, etc. without losing reactivity. Apart from these exceptions, it is as I said at the beginning.

Currently this is possible by using web-components. If you like to make the client do the heavy lift, you can do that using the web-components and keep the pages as simple as possible. Feel free to open a discussion on github issues (https://github.com/brisa-build/brisa/issues) if you are missing anything.

Thanks for reporting @dewey. We are using Github for keeping track of all issues, the Brisa team will appreciate if you could report it to https://github.com/brisa-build/brisa/issues :pray: