Benjamin Bender

@alexander-akait implementation of a CI-workflow shouldn't be part of this PR imho. Separate topic, separate PR.

as we cant add to this pr, here is a separate one: https://github.com/YozhikM/stylelint-a11y/pull/67

Additionally: The tests are clean for stylelint 14, but the (dev-)deps are vastly outdated and full security-issues and would need a serious overhault. This, in turn, would need a decision...

quick note on my efforts regarding `react-query`: I'm thinking about abandoning my efforts as I start to realize that its not a great fit into the sveltekit-ecosystem in the first...

> Is it possible that there isn't something already done that works regardless of the framework (Svelte, Vue, React)? The problem here is that it needs quite a bit of...

Pseudo-code in my head could be something like the following: (problem: it has many opinions about the backend-code/api) ```svelte import type { Initial } from '$lib/package-naming-is-hard'; import { serverQueryAndGetOptions, queryDataInBrowserIfNeededAndCreateForm...

Nope, as I said: too opinionated. Besides that, let them finish v1 and go on from there ^^

Back to topic: I don't think a lib should support an array as key(!). The HTTP-Spec is clear about the mapping between a URL and a resource. I think a...

@ConsoleTVs I would advise to have a look at varnish or haproxy (http caching-proxies) and their caching-options as they should be very in line with the http-spec.

@frederikhors reminds me of turbolinks from rails back in the days ;) But as the article itself states: this basic technique is already used by almost every SPA (incl. sveltekit)...