w2ui VS frontend-maven-plugin

If you are already using jquery , take a look at https://github.com/vitmalina/w2ui

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.

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:

There is always this excelent maven plugin: https://github.com/eirslett/frontend-maven-plugin that pretty much installs and runs whatever you need in the front end. It's perfect when you don't have control over whats installed in the company CI server.