For what it's worth, some time ago, I worked out a configuration with
Angular 2 that did just fine with the usual angular tools, standard angular
serving with hot reloading (as long as the java process was running
separately to answer requests) etc. The "admin" section of my java web-app
starter ki
FWIW I wouldn't veto Node being required to do the front-end build,
although I wouldn't love it either. Primary requirement is that it not be
a component of the production delivery -- glad to see it would not be. And
that anyone could do a build (by adding CLI flags to the build) to not
build the
Hi
Thanks for the clarification. It matches exactly my expectations - during
development you
use whatever fancy dev tools includinga nodejs backend to serve the app, but
at the end
it is bundled into static artifacts like today's UI.
I can understand how your initial statement was interpreted
> Can you summarize for us non-UI folks why a NodeJS server process
would be required? (I had to drop early from the last Virtual Meetup,
so I think I missed this. And most folks on this list weren't there
at all.). I'll be the first to admit to a lack of standing when it
comes to UI stuff, but i
Hi Marcus,
Can you summarize for us non-UI folks why a NodeJS server process
would be required? (I had to drop early from the last Virtual Meetup,
so I think I missed this. And most folks on this list weren't there
at all.). I'll be the first to admit to a lack of standing when it
comes to UI st
