Joachim Viide

This PR is rather outdated. Closing this.

I believe this can be closed. Computeds don't need to be explicitly disposed anymore since @preact/signals-core v1.2.0.

@Baroshem Good points, and great to see you here! I re-enabled the request size limiter, as there doesn't seem to be any routes in Elk that would require large request...

@Baroshem I agree, rate limiting could be left to the infrastructure in this case. As far as I know Elk itself doesn't serve routes that need to be protected from...

The Access-Control-Allow-Origin failures are likely not related to nuxt-security, but mas.to's CORS policy blocking those requests to the /nodeinfo/2.0 endpoint. These nodeinfo requests were added in [these lines](https://github.com/elk-zone/elk/commit/2e7979817a539496925bb0b897fdee1165dfd133#diff-6dce569642d93f4147fe0b2397b2f17dd10c97cce950855577e8bbc589c5b964R120-R124). Disabling nuxt-security...

@osmaa Does the dev mode work for you again after https://github.com/elk-zone/elk/commit/3050350f25f7a25442bf015a2531c631b6e36331?

Great 🙂 Thanks to @danielroe and @antfu for fixing the dev mode!

Interesting. Can you elaborate on your use-case for the described functionality? In our work the use-case for Valita has been validating (& parsing) data from external sources, like user input...

Hello. Unfortunately I haven't had the chance to spend time on this issue. However, I'd like to quickly point out some things: 1. Similarly to Zod, `v.string().default("john")` is functionally equivalent...

@ArnaudBarre `.map()` can't return validation errors, but `.chain()` can: ```ts v.unknown().chain((x) => x === 1 ? v.ok(x) : v.err("bad value")); ```