From: Bnyro <Bnyro@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] pnpm: update to 8.12.0.
Date: Mon, 11 Dec 2023 20:55:55 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47696@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 464 bytes --]
There is a new pull request by Bnyro against master on the void-packages repository
https://github.com/Bnyro/void-packages pnpm
https://github.com/void-linux/void-packages/pull/47696
pnpm: update to 8.12.0.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
A patch file from https://github.com/void-linux/void-packages/pull/47696.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-pnpm-47696.patch --]
[-- Type: text/x-diff, Size: 1384 bytes --]
From 48f1168e0c5941f4fed629dc154821510c6d6bf0 Mon Sep 17 00:00:00 2001
From: Bnyro <bnyro@tutanota.com>
Date: Mon, 11 Dec 2023 20:41:45 +0100
Subject: [PATCH] pnpm: update to 8.12.0.
---
srcpkgs/pnpm/template | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/srcpkgs/pnpm/template b/srcpkgs/pnpm/template
index a06709331100f..1b882eacf1764 100644
--- a/srcpkgs/pnpm/template
+++ b/srcpkgs/pnpm/template
@@ -1,6 +1,6 @@
# Template file for 'pnpm'
pkgname=pnpm
-version=8.11.0
+version=8.12.0
revision=1
build_style=fetch
hostmakedepends="nodejs jq"
@@ -10,17 +10,13 @@ maintainer="Bnyro <bnyro@tutanota.com>"
license="MIT"
homepage="https://pnpm.io/"
distfiles="https://registry.npmjs.org/pnpm/-/pnpm-${version}.tgz"
-checksum=5858806c3b292cbec89b5533662168a957358e2bbd86431516d441dc1aface89
+checksum=553e4eb0e2a2c9abcb419b3262bdc7aee8ae3c42e2301a1807d44575786160c9
python_version=3
do_install() {
npm install -g --user root --prefix "${DESTDIR}/usr" "${XBPS_SRCDISTDIR}/${pkgname}-${version}/${pkgname}-${version}.tgz"
local _npmdir="${DESTDIR}/usr/lib/node_modules/${pkgname}"
- # Sort and cleanup package.json
- jq '.|=with_entries(select(.key|test("_.+")|not))' "$_npmdir/package.json" > "$_npmdir/package.json"
- chmod 644 "$_npmdir/package.json"
-
# Delete JS SourceMaps
find "${DESTDIR}/usr/lib" -depth -name '*.map' -delete
next reply other threads:[~2023-12-11 19:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 19:55 Bnyro [this message]
2023-12-13 7:11 ` kwshi
2023-12-13 7:15 ` [PR REVIEW] " kwshi
2023-12-13 13:15 ` Bnyro
2023-12-13 13:16 ` Bnyro
2023-12-13 13:17 ` Bnyro
2023-12-13 17:45 ` [PR PATCH] [Merged]: " classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47696@inbox.vuxu.org \
--to=bnyro@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).