Bug 33033

ADVISORY NOTICE PROPOSAL
========================
Nodejs 20.12.0 packages bring the new active LTS branch and fix bugs


Description
Nodejs 20 is the new active LTS branch. This update allows to switch to it.
Many bugs are fixed and more detailed information can be found following the links listed as references.

yarn package is updated to 1.22.22 and built with npm 10.5.0

           
References
https://bugs.mageia.org/show_bug.cgi?id=33033
https://github.com/nodejs/node/releases/tag/v20.0.0
https://github.com/nodejs/node/releases/tag/v20.1.0
https://github.com/nodejs/node/releases/tag/v20.2.0
https://github.com/nodejs/node/releases/tag/v20.3.0
https://github.com/nodejs/node/releases/tag/v20.3.1
https://github.com/nodejs/node/releases/tag/v20.4.0
https://github.com/nodejs/node/releases/tag/v20.5.0
https://github.com/nodejs/node/releases/tag/v20.5.1
https://github.com/nodejs/node/releases/tag/v20.6.0
https://github.com/nodejs/node/releases/tag/v20.6.1
https://github.com/nodejs/node/releases/tag/v20.7.0
https://github.com/nodejs/node/releases/tag/v20.8.0
https://github.com/nodejs/node/releases/tag/v20.8.1
https://github.com/nodejs/node/releases/tag/v20.9.0
https://github.com/nodejs/node/releases/tag/v20.10.0
https://github.com/nodejs/node/releases/tag/v20.11.0
https://github.com/nodejs/node/releases/tag/v20.11.1
https://github.com/nodejs/node/releases/tag/v20.12.0
https://github.com/yarnpkg/yarn/releases/tag/v1.22.22


SRPMS
9/core
nodejs-20.12.0-1.mga9.src.rpm
yarnpkg-1.22.22-0.10.5.0.1.mga9.src.rpm

    
PACKAGES FOR QA TESTING
=======================
For x86_64:
v8-devel-11.3.244.8.mga9-2.mga9.x86_64.rpm
nodejs-20.12.0-1.mga9.x86_64.rpm
nodejs-devel-20.12.0-1.mga9.x86_64.rpm
npm-10.5.0-1.20.12.0.1.mga9.x86_64.rpm
nodejs-docs-20.12.0-1.mga9.noarch.rpm
nodejs-libs-20.12.0-1.mga9.x86_64.rpm
yarnpkg-1.22.22-0.10.5.0.1.mga9.noarch.rpm

Assignee: chb0 => qa-bugs

MGA9-64 Plasma Wayland on HP-Pavillion
No installation issues.
Ref bug 32176 for testing
$ npm ls -g
/usr/lib
├── b64@4.1.2
├── boom@7.2.0
├── bounce@1.2.3
├── corepack@0.25.2
├── cryptiles@4.1.1
├── hawk@7.0.10
├── hoek@6.1.2
├── npm@10.5.0
├── sntp@3.0.1
├── teamwork@3.0.3
└── yarn@1.22.22

$ npm ls
/home/tester9
└── (empty)

$ npm install express

added 64 packages in 9s

12 packages are looking for funding
  run `npm fund` for details

$ npm ls
tester9@ /home/tester9
└── express@4.19.2

$ npm install express5
npm WARN deprecated string-similarity@4.0.4: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

added 48 packages, and audited 113 packages in 12s

15 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

$ ls node_modules
 abstract-logging/       escape-html/                  function-bind/              negotiator/               safe-regex2/
 accepts/                es-define-property/           get-intrinsic/              object-inspect/           secure-json-parse/
 ajv/                    es-errors/                    gopd/                       on-finished/              semver/
 archy/                  etag/                         hasown/                     parseurl/                 semver-store/
 array-flatten/          express/                      has-property-descriptors/   path-to-regexp/           send/
 atomic-sleep/           express5/                     has-proto/                  pino/                     serve-static/
 avvio/                  fast-content-type-parse/      has-symbols/                pino-std-serializers/     set-cookie-parser/
 body-parser/            fast-decode-uri-component/    http-errors/                process-warning/          set-function-length/
 bytes/                  fast-deep-equal/              iconv-lite/                 proxy-addr/               setprototypeof/
 call-bind/             '@fastify'/                    inherits/                   punycode/                 side-channel/
 content-disposition/    fastify/                      ipaddr.js/                  qs/                       sonic-boom/
 content-type/           fast-json-stable-stringify/   json-schema-traverse/       queue-microtask/          statuses/
 cookie/                 fast-json-stringify/          light-my-request/           quick-format-unescaped/   string-similarity/
 cookie-signature/       fastq/                        lru-cache/                  range-parser/             tiny-lru/
 debug/                  fast-redact/                  media-typer/                raw-body/                 toidentifier/
 deepmerge/              fast-safe-stringify/          merge-descriptors/          require-from-string/      type-is/
 define-data-property/   finalhandler/                 methods/                    ret/                      unpipe/
 depd/                   find-my-way/                  mime/                       reusify/                  uri-js/
 destroy/                flatstr/                      mime-db/                    rfdc/                     utils-merge/
 ee-first/               forwarded/                    mime-types/                 safe-buffer/              vary/
 encodeurl/              fresh/                        ms/                         safer-buffer/             yallist/

$ node main.js
node:internal/modules/cjs/loader:1146
  throw err;
  ^

Error: Cannot find module '/home/tester9/main.js'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1143:15)
    at Module._load (node:internal/modules/cjs/loader:984:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:135:12)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v20.12.0

I haven't seen that before, did I miss something???
I  understand from bug 32341 that the yarnpkg is used by those commands and does not need separate testing, correct???

CC: (none) => herman.viaene

Thanks Herman for your tests.

The error states: Cannot find module '/home/tester9/main.js'

Should it be provided or is it created?

For yarn, it is a npm wrapper, at first. In my opinion, installation update is enough, except if you are used to build a specific package with it already.

Created attachment 14488 [details]
Test file

(In reply to christian barranco from comment #3)
> Thanks Herman for your tests.
> 
> The error states: Cannot find module '/home/tester9/main.js'
> 
> Should it be provided or is it created?

I am not sure about that, I found that issue too, but then I search for a simple example and get the one in the attachment

node server.js 
Server running at http://127.0.0.1:3000/


http://127.0.0.1:3000/

Shows: Hello World

(In reply to katnatek from comment #4)
> Created attachment 14488 [details]
> Test file
> 
> (In reply to christian barranco from comment #3)
> > Thanks Herman for your tests.
> > 
> > The error states: Cannot find module '/home/tester9/main.js'
> > 
> > Should it be provided or is it created?
> 
> I am not sure about that, I found that issue too, but then I search for a
> simple example and get the one in the attachment
> 
> node server.js 
> Server running at http://127.0.0.1:3000/
> 
> 
> http://127.0.0.1:3000/
> 
> Shows: Hello World

Yes, I have a similar example and it works out.

Validating.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2024-0119.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED