You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Chris Sampson <ch...@naimuri.com.INVALID> on 2023/10/10 19:15:57 UTC
[discuss] NiFi 2 and Node.js version
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
chris.sampson@naimuri.com
Re: [discuss] NiFi 2 and Node.js version
Posted by Joe Witt <jo...@gmail.com>.
My two cents on whether this is a 2.x tied thing is that it doesn't seem
like we're talking about changing the user's experience in either case here
so it should not really be a 2.x blocker. More than anything it sounds
like we should/need/want to do this to be on a more
maintainable/supportable implementation of the UI and there sounds like a
path to bring this in which should be a non issue for the user. So if that
understanding is correct I'd say there is no need to correlate this with a
2.x release. Definitely if we were talking about a different user
experience that would change my thoughts though.
Thanks
On Tue, Oct 10, 2023 at 2:15 PM Chris Sampson
<ch...@naimuri.com.invalid> wrote:
> Matt,
>
> Thanks for correcting my misunderstanding around the utilities in the
> build. It sounds like updating the versions of node & npm used for the
> build should be a separate effort to updating the UI, which it appears
> you're making good headway with.
>
> It seems the question for NiFi 2.x is whether to upgrade these tool
> versions in the build.
>
> Exciting to see the move to newer UI technologies, and hopefully a simpler
> dev experience around UI changes.
>
> On Tue, 10 Oct 2023, 21:44 Matt Gilman, <ma...@gmail.com> wrote:
>
> > 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
> > <ch...@naimuri.com.invalid> 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
> > > chris.sampson@naimuri.com
> > >
> > >
> > >
> >
>
Re: [discuss] NiFi 2 and Node.js version
Posted by Chris Sampson <ch...@naimuri.com.INVALID>.
Matt,
Thanks for correcting my misunderstanding around the utilities in the
build. It sounds like updating the versions of node & npm used for the
build should be a separate effort to updating the UI, which it appears
you're making good headway with.
It seems the question for NiFi 2.x is whether to upgrade these tool
versions in the build.
Exciting to see the move to newer UI technologies, and hopefully a simpler
dev experience around UI changes.
On Tue, 10 Oct 2023, 21:44 Matt Gilman, <ma...@gmail.com> wrote:
> 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
> <ch...@naimuri.com.invalid> 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
> > chris.sampson@naimuri.com
> >
> >
> >
>
Re: [discuss] NiFi 2 and Node.js version
Posted by Matt Gilman <ma...@gmail.com>.
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
<ch...@naimuri.com.invalid> 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
> chris.sampson@naimuri.com
>
>
>