frontend-maven-plugin VS hotwire-rails

Install Node.js Frontend Maven Plugin Gradle Plugin for Node

To build and package your React app with Maven, you can use the frontend-maven-plugin and Maven's profiles to activate it. Add properties for versions and a section to your pom.xml.

In JavaScript land this stuff is done via npm instead. There is a tool for bridging Maven and NPM land stuff https://github.com/eirslett/frontend-maven-plugin but then you are really talking about maintaining two complete stacks. At some point then you might as well just check out something like SvelteKit and Prisma.

Ever considered using eirslett/frontend-maven-plugin? It kind of takes care of a lot of heavy loading, such as setting the environment in order for your project to be built correctly.

You should be able to get away with maven frontend plugin. It will run scripts in your package.json. from there make sure your build output goes in the right place, probably resources/META-INF or something like that.

Sass is an interesting language for generating CSS files that I'm currently trying to play around with. Unfortunately, the existing sass-maven-plugin are based on obsolete implementations, and adding a dependency on npm seems really cumbersome.

3) Bunding into a .jar file : packaging the frontend with the backend into a single JAR file was very confusing. I found the solution using two maven plugins. The first plugin was frontend-maven-plugin which down loads everything that our frontend needs and runs the build command. The second plugin was the Apache Maven Resources Plugin which handles the copying of project resources to the output directory. The combination of these two plugins will give us the ability to run the command of mvnw clean package and have an executable JAR file in the output directory, which we can then execute.

The frontend-maven-plugin is useful to install NodeJS and NPM on the phase of Maven project build. First you add it to POM.xml file:

This is my first time posting here. I have a project that requires me to use Maven (pom.xml) for the build process. I have been using https://github.com/eirslett/frontend-maven-plugin for quite a while and really like it. The frontend-maven-plugin is really neat because it downloads node/npm and saves is in a temporary location within the repo and those local node/npm executables are then used to run certain commands. That way, you can guarantee that the environment running the build has the necessary (pinned to a version) dependencies.

Applications generated with Rails 7 will get Turbo and Stimulus (from Hotwire) by default, instead of Turbolinks and UJS. Hotwire is a new approach that delivers fast updates to the DOM by sending HTML over the wire.

For Ajax-y stuff, I am really excited by the new crop of "HTML-as-a-Service" or "HTML-over-the-wire."

https://htmx.org/

https://hotwired.dev/

For all the turbo/stimulus/hotwire mix, you want to add a new feature just for the sake of adding it? or do you have a use case that fits the feature? if you have then you probably already have an implementation with a different technology (stimulus reflex? some custom websockets or ajax implementation? something with anycable?) and you have to check how to migrate from that technology to hotwire. If you just want to use the feature with no real need for it to practice then just pick any tutorial from the internet (like the intro in the official website https://hotwired.dev).

I was recently interested in similar topic. Here are 3 similar solutions I found:

* https://htmx.org/

* https://unpoly.com/

* https://hotwired.dev/

My personal preference is Unpoly (the idea of "layers" is awesome). But the best explanation of concept as a whole (HATEOAS, keeping app state on server using partial page updates, etc) is at HTMX homepage, and in these essays:

* https://htmx.org/essays/hateoas/

* https://htmx.org/essays/locality-of-behaviour/

At the end of 2020 the Basecamp team released a collection of Javascript libraries called Hotwire. Modern web stacks have popularized javascript-rendered front ends and JSON transmissions. Hotwire's primary motivation is to reduce the Javascript footprint and allow application front ends to be created in primarily HTML. It pairs very nicely with the Ruby on Rails ideology and is often demonstrated in that context. I aim to write a series on how Hotwire can be used in any application to simplify development and reduce the need for heavy Javascript downloads. Hotwire currently consists of two javascript libraries: Turbo and Stimulus. The first part of this series introduces Turbo.

I've been doing that a while until I just got sock of the JS spagetti and often duplicated code and went full on Angular CSR and never looked back. That being said, I've been seeing a lot recently about Laravel's Livewire and Symfony and Ruby on Rail's integration with Hotwire (stimulus+turbo).