npm based packages omit dependencies since Yocto 5.1

["Böszörményi Zoltán" <zboszor@gmail.com>]

Hi,

I have a minimalistic recipe for pm2 (https://www.npmjs.com/package/pm2):
==================================
node-pm2_5.3.1.bb
==================================
SUMMARY = "Production process manager for Node.JS applications with a built-in load balancer."
HOMEPAGE = "http://pm2.keymetrics.io/"
LICENSE = "AGPL-3.0-or-later"
LIC_FILES_CHKSUM = "file://GNU-AGPL-3.0.txt;md5=9f9fa01c099265d62f73735e404ff8bb"

SRC_URI = " \
     npm://registry.npmjs.org/;package=pm2;version=${PV} \
     npmsw://${THISDIR}/${BPN}/npm-shrinkwrap.json \
     "

S = "${UNPACKDIR}/npm"

inherit npm

do_install:append () {
         rm -rf ${D}${libdir}/node_modules/pm2/lib/templates/init-scripts/openrc.tpl
}

RDEPENDS:${PN} = "bash"
==================================

Previously this recipe has built and worked correctly under
Yocto 4.3 and 5.0, as in the package included its own internal
dependencies in /usr/lib/node_modules/pm2/node_modules.
Yocto 4.3 ships nodejs 20.8.1, Yocto 5.0 ships nodejs 20.12.2.

With Yocto 5.1 (node 20.18.0) and master (22.12.0), the package
only has the pm2 module contents in /usr/lib/node_modules/pm2
but no dependencies.

It seems that at some point, nodejs 20.x LTS upgraded npm
to a version with a breaking change which now flattens the
dependencies into a single level in /usr/lib/node_modules
from the previously accustomed dependency tree in
/usr/lib/node_modules/pm2/node_modules.

Is there an incantation of EXTRA_OENPM or the npm:// SRC_URI
that would allow either to unflatten the dependency tree, or
include the dependencies as well as the main node module?

Thanks in advance,
Zoltán Böszörményi