Re: node.js -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: node.js
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 31 Aug 2022 08:26:38 -0600
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

I get:

nodejs12.ppc64 : Node.js JavaScript Runtime
nodejs14.ppc64 : Node.js JavaScript Runtime
nodejs16.ppc64 : Node.js JavaScript Runtime
nodejs18.ppc64 : Node.js JavaScript Runtime
nodever.noarch : Node.js Version Manager

Try yum clean all and search again yum search node

On Wed, Aug 31, 2022 at 6:55 AM Brad Stone <bvstone@xxxxxxxxx> wrote:

Does it take IBM a while to get the latest version on there?

On Wed, Aug 31, 2022 at 6:51 AM Bryan Dietz <bdietz400@xxxxxxxxx> wrote:

when you do yum set it up, it looks like
nodejs14-14.19.1-1.ibmi7.2.ppc64.rpm
is the latest(last) available.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: node.js , Brad Stone

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.