From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Johan Oudinet <johan.oudinet@gmail.com>
Cc: Daniel Price <daniel.price@gmail.com>,
Thomas Claveirole <thomas.claveirole@green-communications.fr>,
Martin Bark <martin@barkynet.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/nodejs: introduce BR2_PACKAGE_HOST_NODEJS_COREPACK
Date: Mon, 26 Sep 2022 12:24:57 +0200 [thread overview]
Message-ID: <20220926122457.1ae898b3@windsurf> (raw)
In-Reply-To: <CAJtjsKbXry53n6HTcvV9jPyxJ4fcCbryAn7Vtk_8i=Q9qfed5g@mail.gmail.com>
On Mon, 26 Sep 2022 12:17:04 +0200
Johan Oudinet <johan.oudinet@gmail.com> wrote:
> That's a good point. I'll report this issue to forge developers. Every
> npm packages should have a package-lock.json file in their repository.
See https://github.com/digitalbazaar/forge/issues/1005.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-09-26 10:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 17:40 [Buildroot] [PATCH 0/2] Update host-nodejs and build vuejs from source Thomas Claveirole
2022-09-13 17:40 ` [Buildroot] [PATCH 1/2] package/nodejs: introduce BR2_PACKAGE_HOST_NODEJS_COREPACK Thomas Claveirole
2022-09-25 19:47 ` Thomas Petazzoni
2022-09-25 19:53 ` Thomas Petazzoni
2022-09-26 9:04 ` Thomas Claveirole
2022-09-26 10:01 ` Thomas Petazzoni
2022-09-26 10:17 ` Johan Oudinet
2022-09-26 10:24 ` Thomas Petazzoni [this message]
2023-04-16 19:48 ` Yann E. MORIN
2022-09-13 17:40 ` [Buildroot] [PATCH 2/2] package/vuejs: bump to version 3.2.39 Thomas Claveirole
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=20220926122457.1ae898b3@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=daniel.price@gmail.com \
--cc=johan.oudinet@gmail.com \
--cc=martin@barkynet.com \
--cc=thomas.claveirole@green-communications.fr \
/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