Server-Side Rendering with Spring Boot
Understanding the shared steps in the project setup is crucial before delving into the specifics of each client-augmenting technology. My requirements from the last post where quite straightforward:
It’s important to note that the technology I’ll be detailing, except Vaadin, follows a similar approach. Vaadin, with its unique paradigm, really stands out among the approaches.
The framework’s responsibility is to expose the assets under a URL. For example, Spring Boot does it in the WebMvcAutoConfiguration class:
Inside the JAR, you can reach assets by their respective path and name. The agreed-upon structure is to store the assets inside resources/webjars/<library>/<version>. Here’s the structure of the alpinejs-3.14.1.jar:
Developers release client-side libraries quite often. When you change a dependency version in the POM, you must change the front-end path, possibly in multiple locations. It’s boring, has no added value, and you risk missing a change.
