2 unstable releases
0.2.3 | Apr 21, 2022 |
---|---|
0.1.9 | Apr 4, 2022 |
0.1.7 |
|
#21 in #package-json
49 downloads per month
12KB
138 lines
Alpakr CLI 🦙
A simple package lookup service that isn't too strict about its inputs. Paste a snippet of names and Alpakr will do it's best to provide info about the packages.
Conjugation of 'All' and 'Packager' and pronounced the friendly fury alpaca.
\ ăl-păk′ə \
Install
cargo install alpakr-cli
Usage
Copy paste a fragment from a Cargo.toml, package.json or python requirments.txt file and pipe it to alpakr
.
$ echo "
console = "0.15.0"
base64 = "0.13.0"
serde = { version = "1.0", features = ["derive"] }" | alpakr
Example output:
console -> A terminal and console abstraction for Rust
https://crates.io/crates/console
base64 -> encodes and decodes base64 as bytes or utf8
https://crates.io/crates/base64
serde -> A generic serialization/deserialization framework
https://crates.io/crates/serde
Note: for best result paste at least one full line, but more is better.
Other ways to query
$ grep -A 3 "console" Cargo.toml | alpakr
$ alpakr <enter>
console = "0.15.0"
base64 = "0.13.0"
serde = { version = "1.0", features = ["derive"] }
<ctrl-d>
# If you are on Mac use `pbpaste`
$ pbpaste | alpakr
Options
--verbose
: see encoded payload and full response--json
: output as JSON
Supported package managers
- cargo (crates.io)
- cargo compiling (crates.io)
- composer (packagist.org)
- gem (rubygems.org)
-
gomod (pkg.go.dev) - npm (npmjs.com)
- pip (pypi.org)
Motivation
In short. I read a lot of code in many different languages. Part of that is looking into what third party packages are used. This can be by reading package.json files or skimming through the text when compiling a Rust program. I wanted to make it easier to learn about packages I don't know about.
Dependencies
~9–24MB
~330K SLoC