Chris, Thanks for raising this. Node.js (and npm) are used at build time to package the front-end applications. Bumping those versions should be doable. However, the front end still uses a lot of legacy and now unsupported dependencies and also requires updating. This aspect is a much larger effort. There is a JIRA [1] filed for migrating the front end to current versions of these dependencies. That work is underway and things are progressing nicely. The JIRA also lays out a high-level plan for introducing this change without impacting the existing UI until it's fully ready.
[1] https://issues.apache.org/jira/browse/NIFI-11481 On Tue, Oct 10, 2023 at 3:16 PM Chris Sampson <[email protected]> wrote: > The main focus of NiFi 2.x has so far been to upgrade Java to JDK 21 and > remove deprecated/unmaintained code and artefacts. > > The NiFi & NifI Registry UIs are currently using Node.js v16, which is an > LTS release, but is imminently due to be end of life [1]. Node.js v18 has > been the current LTS release since October 2022, although v20 is about to > take over that spot. > > Should the NiFi 2.x milestone include an upgrade of the UI frameworks to > (at least) Node.js v20, or v18 if there are compatibility issues with > dependencies used? > > If this is already on somebody’s roadmap, then great, but I just noticed > this in the pom.xml files and thought it was worth raising. > > > [1]: https://nodejs.dev/en/about/releases/ > > Cheers, > > --- > Chris Sampson > IT Consultant > [email protected] > > >
