frontend-maven-plugin VS Alpine.js

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.

Alpine.js for reactive frontend

✨ In recent months, I have been developing web projects using GOTTHA stack: Go + Templ + Tailwind CSS + htmx + Alpine.js. As soon as I'm ready to talk about all the subtleties and pitfalls, I'll post it on my social networks.

> But honestly, torn towards htmx but undecided.

We are in the middle of migrating from our monster react application into server rendered pages (with jinja2). The velocity at which we are able to ship and the reduction of complexity has been great so far.

Managing client side state for simple things like (is the dropdown open/closed), listening to keyboard events and such can be done with something like alpine-js [1] without all the baggage that something like react brings.

It appears this is already the trend with JS frameworks too - with server side rendering being the new norm.

[1] https://alpinejs.dev/

Sure, you can use any number of JS-avoidance libraries. I'm a fan of Turbo, and there's also htmx, Unpoly, Alpine, hyperscript, swup, barba.js, and probably others.

Direct DOM, but with a library. Specifically AlpineJS since it follows Vue closely in design practices allowing me to scale into a full web application if necessary (basically swapping to Vue takes minimal work). The Morph plugin is specifically what I like using.

If you want more details on the initial setup I encourage you to take a look at the Part I that covers more of the initial implementation. For this portion, I added Prisma as an ORM, a frontend style library called Tachyons, and AlpineJS to handle any client-side interactions. I did this to avoid needing to add a client-side bundler to the build and instead just rely on plain old module imports to compose the frontend. This is now the default for Rails and it is quite nice to not need any additional build tools for the client.

- [swallow-pywebview](https://github.com/rangwea/swallow-pywebview)： Base on [pywebview](https://pywebview.flowrl.com/) using Python，the frontend base on [alpinejs](https://alpinejs.dev/) and [tailwindcss](https://tailwindcss.com/)。

If you’ve followed our other tutorials, you might be familiar with Alpine.js. It’s a lightweight JavaScript library that allows you to add interactivity to your site without writing a single line of JavaScript. It’s incredibly easy to use, and we’ll show you how to make the animation trigger when the user scrolls to it.

The approach is not new, essentially a variation of Knockout, Alpine, and similar "JS-in-HTML" approaches.