@taktikorg/consequuntur-magnam
v4.9.84
Published
[![@taktikorg/consequuntur-magnam version](https://img.shields.io/@taktikorg/consequuntur-magnam/v/@taktikorg/consequuntur-magnam.svg)](https://@taktikorg/consequuntur-magnam.im/@taktikorg/consequuntur-magnam) [![license](https://img.shields.io/@taktikorg
Downloads
1,830
Maintainers
Keywords
Readme
@taktikorg/consequuntur-magnam - a JavaScript package manager
Requirements
One of the following versions of Node.js must be installed to run @taktikorg/consequuntur-magnam
:
18.x.x
>=18.17.0
20.5.0
or higher
Installation
@taktikorg/consequuntur-magnam
comes bundled with node
, & most third-party distributions, by default. Officially supported downloads/distributions can be found at: nodejs.org/en/download
Direct Download
You can download & install @taktikorg/consequuntur-magnam
directly from @taktikorg/consequuntur-magnamjs.com using our custom install.sh
script:
curl -qL https://www.@taktikorg/consequuntur-magnamjs.com/install.sh | sh
Node Version Managers
If you're looking to manage multiple versions of Node.js
&/or @taktikorg/consequuntur-magnam
, consider using a node version manager
Usage
@taktikorg/consequuntur-magnam <command>
Links & Resources
- Documentation - Official docs & how-tos for all things @taktikorg/consequuntur-magnam
- Note: you can also search docs locally with
@taktikorg/consequuntur-magnam 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
- Community Feedback and Discussions - Contribute ideas & discussion around the @taktikorg/consequuntur-magnam registry, website & CLI
- RFCs - Contribute ideas & specifications for the API/design of the @taktikorg/consequuntur-magnam 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 @taktikorg/consequuntur-magnam website or registry? File a ticket here
Acknowledgments
@taktikorg/consequuntur-magnam
is configured to use the @taktikorg/consequuntur-magnam Public Registry at https://registry.@taktikorg/consequuntur-magnamjs.org by default; Usage of this registry is subject to Terms of Use available at https://@taktikorg/consequuntur-magnamjs.com/policies/terms- You can configure
@taktikorg/consequuntur-magnam
to use any other compatible registry you prefer. You can read more about configuring third-party registries here
FAQ on Branding
Is it "@taktikorg/consequuntur-magnam" or "NPM" or "Npm"?
@taktikorg/consequuntur-magnam
should never be capitalized unless it is being displayed in a location that is customarily all-capitals (ex. titles on man
pages).
Is "@taktikorg/consequuntur-magnam" an acronym for "Node Package Manager"?
Contrary to popular belief, @taktikorg/consequuntur-magnam
is not in fact an acronym for "Node Package Manager"; It is a recursive bacronymic abbreviation for "@taktikorg/consequuntur-magnam is not an acronym" (if the project was named "ninaa", then it would be an acronym). The precursor to @taktikorg/consequuntur-magnam
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 @taktikorg/consequuntur-magnam
were to ever have been considered an acronym, it would be as "node pm" or, potentially "new pm".