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/saralahttps://github.com/robsontenorio/vue-api-queryhttps://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 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.
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.
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 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