Github user scottyaslan commented on the issue:
https://github.com/apache/nifi/pull/2269
@yuri1969 you are welcome.
I agree moving to Angular 2+ right now is probably out of scope for this
PR. I just wanted to get the discussion moving forward about how we can offer a
consistent quality UX across the nifi suite of web apps.
For the JS unit tests you should be able to use the nifi registry as an
example. It uses npm and the frontend-maven-plugin to run the karma.conf.js
(https://github.com/apache/nifi-registry/blob/master/nifi-registry-web-ui/pom.xml#L442
and also
https://github.com/apache/nifi-registry/blob/master/nifi-registry-web-ui/src/main/frontend/package.json#L7).
As for optimizing/minifying/bundling the JS/CSS/HTML there are a few
different ways you could go about it. The nifi web site and the nifi registry
both use grunt so there are some options there. The nifi registry uses grunt
along with SystemJS to bundle and minify the client code
(https://github.com/apache/nifi-registry/blob/master/nifi-registry-web-ui/pom.xml#L344).
Nifi itself, however, uses maven and the YUI compressor to produce a client
bundle
(https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/pom.xml#L418).
You will most likely want to follow the way nifi does it.
---
