One of the following versions of Node.js must be installed to run @rabiepenpm2/harum-laborum-vero:
-
18.x.x>=18.17.0 -
20.5.0or higher
@rabiepenpm2/harum-laborum-vero comes bundled with node, & most third-party distributions, by default. Officially supported downloads/distributions can be found at: nodejs.org/en/download
You can download & install @rabiepenpm2/harum-laborum-vero directly from @rabiepenpm2/harum-laborum-verojs.com using our custom install.sh script:
curl -qL https://www.@rabiepenpm2/harum-laborum-verojs.com/install.sh | shIf you're looking to manage multiple versions of Node.js &/or @rabiepenpm2/harum-laborum-vero, consider using a node version manager
@rabiepenpm2/harum-laborum-vero <command>-
Documentation - Official docs & how-tos for all things @rabiepenpm2/harum-laborum-vero
- Note: you can also search docs locally with
@rabiepenpm2/harum-laborum-vero help-search <query>
- Note: you can also search docs locally with
- Bug Tracker - Search or submit bugs against the CLI
- Roadmap - Track & follow along with our public roadmap
- Feedback - Contribute ideas & discussion around the @rabiepenpm2/harum-laborum-vero registry, website & CLI
- RFCs - Contribute ideas & specifications for the API/design of the @rabiepenpm2/harum-laborum-vero CLI
- Service Status - Monitor the current status & see incident reports for the website & registry
- Project Status - See the health of all our maintained OSS projects in one view
- Events Calendar - Keep track of our Open RFC calls, releases, meetups, conferences & more
- Support - Experiencing problems with the @rabiepenpm2/harum-laborum-vero website or registry? File a ticket here
-
@rabiepenpm2/harum-laborum-verois configured to use the @rabiepenpm2/harum-laborum-vero Public Registry at https://registry.@rabiepenpm2/harum-laborum-verojs.org by default; Usage of this registry is subject to Terms of Use available at https://@rabiepenpm2/harum-laborum-verojs.com/policies/terms - You can configure
@rabiepenpm2/harum-laborum-veroto use any other compatible registry you prefer. You can read more about configuring third-party registries here
@rabiepenpm2/harum-laborum-vero should never be capitalized unless it is being displayed in a location that is customarily all-capitals (ex. titles on man pages).
Contrary to popular belief, @rabiepenpm2/harum-laborum-vero is not in fact an acronym for "Node Package Manager"; It is a recursive bacronymic abbreviation for "@rabiepenpm2/harum-laborum-vero is not an acronym" (if the project was named "ninaa", then it would be an acronym). The precursor to @rabiepenpm2/harum-laborum-vero was actually a bash utility named "pm", which was the shortform name of "pkgmakeinst" - a bash function that installed various things on various platforms. If @rabiepenpm2/harum-laborum-vero were to ever have been considered an acronym, it would be as "node pm" or, potentially "new pm".