I came to write this package as I was annoyed by code duplication when writing bespoke requests. Such as: unwrapping data, specifying the endpoint, transforming keys' casing etc. I looked around and saw there was no package that solved my issues and this was a gap in the ecosystem. Evidently I did not look good enough as since then I have found some alternatives: https://github.com/milroyfraser/sarala https://github.com/robsontenorio/vue-api-query https://github.com/DavidDuwaer/Coloquent However I still find that my package is more feature packed and has more elegant solutions (e.g.: relationship handling). I think what's great about this package is that typescript, clean and thorough documentation and self documenting code makes it really easy and fast to talk to your apis no matter the complexity of the data. I hope that this package will serve you just as well as it did in my own personal web applications.

I wish some people did that but for documentation

Found this:

https://svelte.dev/blog/virtual-dom-is-pure-overhead

https://medium.com/@hayavuk/why-virtual-dom-is-slower-2d9b96...

I think it can be classed as an object relation mapping. Although it does a bit more than that, such as tracking changes, attribute management, guarding etc.

This means to me that at the minimum the getting started page has much to improve to make it more accessible/easy to scan.

Data handling framework complementary to backend model systems.

What about tidal subscriptions? Are they any good?

I don't see the argument that it's weakening the JavaScript ecosystem. If anything it enriches it as you have (generally) safer more robust code to work with.

TypeScript is reaching GHC level of configuration flags, builds using it manage to even be slower than many native toolchains, and the team seems to just keep going with crazy type systems ideas, I already lost track of them.

Really, I hope that in a couple of years browsers would just allow for WebIDL integration and that is it.

It's quite common to see a similar concern raised about contemporary versions of the Swift language design (language-nerd lunatics taking over the asylum).

Yep, and Kotlin is just getting whole the Scala refugees.

I'm working on a front-end data handling framework inspired by backend model system (largely laravel) including collections, factories, and much more. It feature rich, extensible (OOP, driver pattern), fully tested, does the right amount of magic, written in typescript. It's gonna be joy to work with...

I worked on this for about 7-8 months now.

Forgot to add it's currently works with rest APIs but planning to add graphql support too among other things

I think you can in 4.1 add --generateTrace and the output path. The result you can inspect in the browser. Also there's -- extendedDiagnistics if I remember correctly that tells you which part of the compilation process takes what time