public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Böszörményi Zoltán" <zboszor@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
	Alexander Kanavin <alex.kanavin@gmail.com>
Subject: Re: [OE-core] npm based packages omit dependencies since Yocto 5.1
Date: Tue, 21 Jan 2025 17:25:59 +0100	[thread overview]
Message-ID: <0f95eab6-489e-4be4-9add-5b0c5b39532a@gmail.com> (raw)
In-Reply-To: <181CB1A49703171B.28835@lists.openembedded.org>

The recent changes in Yocto master with the unmodified recipe didn't help.
But npmsw://...;destsuffix=npm in the recipe did.

Thanks again!

2025. 01. 21. 12:27 keltezéssel, Zoltan Boszormenyi via lists.openembedded.org írta:
> That's it! ;destsuffix=npm helped with Yocto 5.1.
> Thank you very much!
>
> I will re-test with Yocto master and report back.
>
> 2025. 01. 21. 11:53 keltezéssel, Martin Jansa írta:
>> I believe it's the side effect of UNPACKDIR changes, I had to add
>> ;destsuffix=npm in all npmsw:// entries (or ;destsuffix=git where S is
>> set to WORKDIR/git) for dependencies in node_modules to be unpacked
>> where they used to be before.
>>
>> On Tue, Jan 21, 2025 at 11:31 AM Zoltan Boszormenyi via
>> lists.openembedded.org <zboszor=gmail.com@lists.openembedded.org>
>> wrote:
>>> 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
>>>
>>>
>>>
>>>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#210090): https://lists.openembedded.org/g/openembedded-core/message/210090
> Mute This Topic: https://lists.openembedded.org/mt/110731121/3617728
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [zboszor@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>



  parent reply	other threads:[~2025-01-21 16:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21 10:31 npm based packages omit dependencies since Yocto 5.1 Böszörményi Zoltán
2025-01-21 10:33 ` [OE-core] " Alexander Kanavin
2025-01-21 10:53 ` Martin Jansa
2025-01-21 11:27   ` Böszörményi Zoltán
     [not found]   ` <181CB1A49703171B.28835@lists.openembedded.org>
2025-01-21 16:25     ` Böszörményi Zoltán [this message]
2025-01-23  9:11       ` Martin Jansa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0f95eab6-489e-4be4-9add-5b0c5b39532a@gmail.com \
    --to=zboszor@gmail.com \
    --cc=alex.kanavin@gmail.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox