I have been working on Liaison for a year and a half with an obsession — simplifying full-stack development as much as possible.
Typically, a full-stack application is composed of a frontend and a backend running in two different environments that are connected through a web API (REST, GraphQL, etc.)
Separating the frontend and the backend is a good thing, but the problem is that building a web API usually leads to a lot of code scattering, duplication of knowledge, boilerplate, and accidental complexity.
Liaison removes the need of building a web API and reunites the frontend and the backend in a way that you can experience them as a single entity.
On the frontend side, Liaison gives you routing capabilities and object observability so that in most cases you don't need to add an external router or a state manager.
Last but not least, Liaison offers a simple but powerful ORM to make data storage as easy as possible.
Please check out the website, have a look at the documentation, and tell me what you think.
I have been working on Liaison for a year and a half with an obsession — simplifying full-stack development as much as possible.
Typically, a full-stack application is composed of a frontend and a backend running in two different environments that are connected through a web API (REST, GraphQL, etc.)
Separating the frontend and the backend is a good thing, but the problem is that building a web API usually leads to a lot of code scattering, duplication of knowledge, boilerplate, and accidental complexity.
Liaison removes the need of building a web API and reunites the frontend and the backend in a way that you can experience them as a single entity.
On the frontend side, Liaison gives you routing capabilities and object observability so that in most cases you don't need to add an external router or a state manager.
Last but not least, Liaison offers a simple but powerful ORM to make data storage as easy as possible.
Please check out the website, have a look at the documentation, and tell me what you think.