From: Janic Bellmann <contact@janic.dev>
To: "office@proxmox.com" <office@proxmox.com>
Cc: "pve-devel@lists.proxmox.com" <pve-devel@lists.proxmox.com>
Subject: Wiki "Proxmox VE API": community client list for NodeJS is outdated
Date: Thu, 19 Nov 2026 17:56:30 +0000 [thread overview]
Message-ID: <O_vycMjR6qBamiSAQpZ7df4J96Zg05e_nMk0GB7sCDuw1y-jQKQq65-sjzzVv6LXRAPQiU58gbPeRZGluoK1ohIhO3CW4hwMH2cISQMQUYs=@janic.dev> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1301 bytes --]
Hello,
The "Community Maintained -> NodeJS" section of
https://pve.proxmox.com/wiki/Proxmox_VE_API is out of date:
- pvea: the linked GitHub repository (github.com/AmiCole/pvea) returns
404. The last npm release was in July 2020.
- proxmox (npm): no release since February 2023.
I'd suggest removing these two entries and adding:
- @virtbase/proxmox-api: https://proxmox-api.virtbase.com
A TypeScript client generated from the API schema in pve-docs
(currently 9.2.15), covering every endpoint with typed parameters and
responses. A workflow checks daily for new pve-docs releases and
publishes an API changelog. MIT licensed.
cv4pve-api-javascript is still actively maintained and should stay.
One unrelated detail: the Perl entry links to an old search.cpan.org URL
pinned to Net-Proxmox-VE 0.006. https://metacpan.org/dist/Net-Proxmox-VE
would always show the current release.
I'm the maintainer of @virtbase/proxmox-api. Happy to make the edit myself
if you can give me wiki access.
Best regards,
Janic
--Janic Bellmann
Developer & Founder, Virtbase
https://janic.dev | https://virtbase.com
GitHub: https://github.com/masterjanic
LinkedIn: https://www.linkedin.com/in/janic-bellmann
PGP: 01A9 461F F583 83F9 173B D8A3 9539 6995 CF5E 7932
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 323 bytes --]
reply other threads:[~2026-11-20 13:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='O_vycMjR6qBamiSAQpZ7df4J96Zg05e_nMk0GB7sCDuw1y-jQKQq65-sjzzVv6LXRAPQiU58gbPeRZGluoK1ohIhO3CW4hwMH2cISQMQUYs=@janic.dev' \
--to=contact@janic.dev \
--cc=office@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.