OPAM-SEARCH(1)

📦
version 2.6.1 · 8 versions
, in arch rolling, fedora 44

💖 NAME 💖

opam-search — bestie, it's literally just an alias for list --search. that's the whole thing. 💅

📜 SYNOPSIS 📜

opam search [--check] [--no-depexts] [--silent] [OPTION]… [PATTERNS]…

🦋 DESCRIPTION 🦋

okay so opam search is just a cute little alias for opam list --search. no cap, same energy, same behaviour. 😌

want the real tea? run opam list --help. all the details live over there. 🫶

🎀 PACKAGE SELECTION OPTIONS 🎀

narrowing down which packages show up. pick your filter, pick your vibe:

  • --coinstallable-with=PACKAGES — only list packages that are compatible with all of PACKAGES. everyone in the group chat has to get along, fr.
  • --conflicts-with=PACKAGES — list packages that have declared conflicts with at least one of the packages you gave. and it's not just direct beef — this includes conflicts defined from the packages in the list, from the other package, or by a common conflict-class: field. messy. 💀
  • --depends-on=PACKAGES — list only the packages that depend on one of the (comma-separated) PACKAGES.
  • --depopts — include optional dependencies in dependency requests.
  • --dev — include development packages in dependencies.
  • --field-match=FIELD:PATTERN — filter packages that have a match for PATTERN on the given FIELD.
  • --has-flag=FLAG — only include packages that have the given flag set. package flags are one of: light-uninstall verbose plugin compiler conf.
  • --has-tag=TAG — only includes packages that have the given tag set.
  • --no-switch — list what's available from the repositories, without consideration for the current (or any other) switch. no installed or pinned packages, none of that. just the repos, raw. ✨
  • --nobuild — exclude build dependencies (they're included by default, fyi).
  • --or — instead of selecting packages that match all the criteria, select packages that match any of them. choose-your-own-adventure mode.
  • --owns-file=FILE — finds the installed packages responsible for installing the given FILE. detective mode. 🔍
  • --post — include dependencies tagged as post.
  • --recursive — with --depends-on and --required-by, display all transitive dependencies rather than just the direct ones. the whole tree, not just the branches you can see.
  • --repos=REPOS — include only packages that took their origin from one of the given repositories. heads up: unless no-switch is also specified, this excludes pinned packages.
  • --required-by=PACKAGES — list only the dependencies of the (comma-separated) PACKAGES.
  • --resolve=PACKAGES — restrict to a solution to install the (comma-separated) PACKAGES, i.e. a consistent set of packages including those. and ngl this is subtly different from --required-by --recursive, which is more predictable and can't fail, but lists all dependencies independently without ensuring consistency. without --installed, the answer is self-contained and independent of the current installation. with --installed, it's computed from the set of currently installed packages. --no-switch further makes the solution independent from the currently pinned packages, architecture, and compiler version. oh and — the combination with --depopts is not supported. 🙅
  • -t, --with-test, --test — include test-only dependencies.
  • --with-dev-setup — include developer only dependencies.
  • --with-doc, --doc — include doc-only dependencies.

🌈 OUTPUT FORMAT OPTIONS 🌈

this is the aesthetic section. how do you want it to look? 💅

  • --columns=COLUMNS — select the columns to display, from these: name, version, package, synopsis, synopsis-or-target, description, <field>:, installed-version, pin, source-hash, opam-file, all-installed-versions, available-versions, all-versions, repository, installed-files, vc-ref, depexts. the special form <field>: (a field name followed by a colon, e.g., license:) selects an arbitrary field. default is name when --short is present, and name, installed-version, synopsis-or-target otherwise.
  • -e, --external, --depexts — instead of displaying the packages, display their external dependencies that are associated with the current system. this excludes other display options. and honestly? rather than using this directly, you should probably head for the depext plugin, which will use your system package management system to handle the installation of the dependencies. run opam depext. 👑
  • --normalise — print the values of opam fields normalised.
  • -S, --sort — sort the packages in dependency order (i.e. an order in which they could be individually installed). topologically slaying. ✨
  • -s, --short — don't print a header, and sets the default columns to name only. if you need package versions included, use --columns=package instead.
  • --separator=STRING (absent= ) — set the column-separator string. yes, the default is a literal space.
  • -V, --all-versions — normally, when multiple versions of a package match, only one is shown in the output (the installed one, the pinned-to one, or, failing that, the highest one available or the highest one). this flag disables that behaviour and shows all matching versions. it also changes the default display format to include package versions instead of just package names (including when --short is set). and it's automatically turned on when a single non-pattern package name is provided on the command-line. 💫
  • --vars=[VAR=STR,...] — define the given variable bindings. typically useful with --external to override the values for arch, os, os-distribution, os-version, os-family.
  • --wrap — wrap long lines. the default is to truncate when displaying on a terminal, or to keep as is otherwise.

🧚 ORDER-SENSIBLE SELECTORS 🧚

these ones care about where a package sits in the order of things:

  • -a, --available — list only packages that are available on the current system.
  • -A, --all — include all, even uninstalled or unavailable packages. no filter, no judgement. 💜
  • --base — removed in 2.1, use --invariant instead.
  • -i, --installed — list installed packages only. this is the default when no further arguments are supplied.
  • --installable — list only packages that can be installed on the current switch. 👀 careful though: this calls the solver and may be more costly. also a package depending on an unavailable package may be available, but is never installable.
  • --invariant — list only the immutable base of the current switch (i.e. invariant packages).
  • --latests-only — list only the latest version of each package.
  • --pinned — list only the pinned packages.
  • --roots, --installed-roots — list only packages that were explicitly installed, excluding the ones installed as dependencies. the main characters only. 👑

🍓 ARGUMENTS 🍓

  • PATTERNS — package patterns with globs. unless --search is specified, they match against a NAME or NAME.VERSION.

💅 OPTIONS 💅

the last little trio, bestie:

  • --check — don't write anything in the output. exit with return code 0 if the list is not empty, 1 otherwise.
  • --no-depexts — disable external dependencies handling for the query. this can be used to include packages that are marked as unavailable because of an unavailable system dependency.
  • --silent — removed in 2.1, use --check instead.

✨ COMMON OPTIONS ✨

Okay bestie, these options are literally common to all commands. Like, every single one. No cap. 💅

  • --best-effort — okay so if you can't install every single package you asked for, this says "don't be dramatic, just install as many as you can". 💪 But heads up: not every external solver is gonna support this (recent versions of aspcud or mccs should, though). It's the same as setting the $OPAMBESTEFFORT environment variable. fr fr.
  • --cli=MAJOR.MINOR (absent=2.6) — this lets you use the command-line interface syntax and semantics of MAJOR.MINOR. It's for when you're doing persistent opam stuff (scripts, blog posts, whatever), so any opam in the same MAJOR series will act like the MINOR release you picked. 🎀 But note: this flag didn't exist in opam 2.0, so if you want the 2.0 CLI, you gotta set the OPAMCLI environment variable to 2.0 instead. iykyk.
  • --color=WHEN — turns on the colors, bestie. 🌈 WHEN has to be one of always, never, or auto. Periodt.
  • --confirm-level=LEVEL — sets the confirmation level. LEVEL must be one of ask, no, yes, or unsafe-yes. You can specify this more than once. If --yes or --no are also given, then the value of the last --confirm-level wins. It's equivalent to setting the $OPAMCONFIRMLEVEL environment variable. 💅
  • --criteria=CRITERIA — lets you set your user preferences for dependency solving for this run. It overrides $OPAMCRITERIA, $OPAMFIXUPCRITERIA, and $OPAMUPGRADECRITERIA. For details on the supported language and the external solvers available, check out http://opam.ocaml.org/doc/External_solvers.html. And for a general guide to using solver preferences, peep http://www.dicosmo.org/Articles/usercriteria.pdf. 📚
  • --cudf=FILENAME — debug option, bestie. It saves the CUDF requests sent to the solver to FILENAME-<n>.cudf, where <n> is the n-th call to the solver during the opam run. 🐛
  • --debug — prints debug messages to stderr. It's the same as setting $OPAMDEBUG to "true". 🔍
  • --debug-level=LEVEL — like --debug, but you can pick the debug level (--debug just sets it to 1). Equivalent to setting $OPAMDEBUG to a positive integer. 🐞
  • --git-version — prints the git version of opam (if it's set, meaning you're using a development version) and then exits. 👋
  • --help[=FMT] (default=auto) — shows this help in format FMT. FMT must be one of auto, pager, groff, or plain. With auto, the format is pager or plain whenever the TERM env var is dumb or undefined. 💁‍♀️
  • --ignore-pin-depends — ignores extra pins required by packages that get pinned, whether manually through opam pin or through opam install DIR. This is equivalent to setting IGNOREPINDEPENDS=true. 🙈
  • --json=FILENAME — saves the results of the opam run in a computer-readable file. If the filename contains the character %, it gets replaced by an index that doesn't overwrite an existing file. Similar to setting the $OPAMJSON variable. 📁
  • --no — answers no to all opam yes/no questions without prompting. See also --confirm-level. Equivalent to setting $OPAMNO to "true". 🙅‍♀️
  • --no-aspcud — removed in 2.1. 💀
  • --no-auto-upgrade — when opam configures or updates a repository written for an earlier opam version (1.2), it internally converts it to the current format. This disables that behavior. Note: repositories should define their format version in a 'repo' file at their root, or they'll be assumed to be in the older format. In any case, it's preferable to upgrade the repositories manually using opam admin upgrade [--mirror URL] when possible. 🚫
  • --no-self-upgrade — opam will replace itself with a newer binary found at OPAMROOT/opam if present. This disables that behavior. 🛑
  • -q, --quiet — disables --verbose. 🤫
  • --root=ROOT — uses ROOT as the current root path. Equivalent to setting $OPAMROOT to ROOT. 🌳
  • --safe, --readonly — makes sure nothing gets automatically updated or rewritten. Super useful for calling from completion scripts, for example. It will fail whenever such an operation is needed; it also avoids waiting for locks, skips interactive questions, and overrides the $OPAMDEBUG variable. Equivalent to setting the $OPAMSAFE environment variable. 🛡️
  • --solver=CMD — specifies the CUDF solver to use for resolving package installation problems. This is either a predefined solver (this version of opam supports builtin-mccs+lp(), builtin-mccs+glpk, builtin-dummy-z3-solver, builtin-0install, aspcud, mccs, aspcud-old, packup), or a custom command that should contain the variables %{input}%, %{output}%, %{criteria}%, and optionally %{timeout}%. Equivalent to setting $OPAMEXTERNALSOLVER. ⚙️
  • --strict — fails whenever an error is found in a package definition or a configuration file. The default is to continue silently if possible. 💥
  • --switch=SWITCH — uses SWITCH as the current compiler switch. Equivalent to setting $OPAMSWITCH to SWITCH. 🔀
  • --use-internal-solver — disables any external solver and uses the built-in one (this requires that opam was compiled with a built-in solver). Equivalent to setting $OPAMNOASPCUD or $OPAMUSEINTERNALSOLVER. 🏠
  • -v, --verbose — be more verbose. One -v shows all package commands; repeat to also display commands called internally (e.g. tar, curl, patch, etc.). Repeating n times is equivalent to setting $OPAMVERBOSE to "n". 🗣️
  • --version — shows version information. 📌
  • -w, --working-dir — whenever updating packages that are bound to a local, version-controlled directory, update to the current working state of their source instead of the last committed state, or the ref they are pointing to. Since the source directory is copied as it is, if it isn't clean it may result in an opam build failure. This only affects packages explicitly listed on the command-line. It can also be set with $OPAMWORKINGDIR. 📂
  • -y, --yes — answers yes to all opam yes/no questions without prompting. See also --confirm-level. Equivalent to setting $OPAMYES to "true". ✅

🌍 ENVIRONMENT 🌍

ok so bestie, opam is deeply into environment variables 💅 like it will read these before you even finish typing, so listen up. Every one of these is listed below.

Quick rule for the boolean girlies: set them to "0", "no", "false" or the empty string to disable them, and "1", "yes" or "true" to enable them. That's it, that's the whole grammar 💖

  • OPAMALLPARENS — surround all filters with parenthesis.
  • OPAMASSUMEDEPEXTS — see option --assume-depexts.
  • OPAMAUTOANSWER — internal use only 🙈 (not for you, babe).
  • OPAMAUTOREMOVE — see remove option --auto-remove.
  • OPAMBESTEFFORT — see option --best-effort.
  • OPAMBESTEFFORTPREFIXCRITERIA — sets the string that must be prepended to the criteria when the --best-effort option is set, and is expected to maximise the opam-query property in the solution.
  • OPAMBUILDDOC — Removed in 2.1. 💀 gone, deceased, rip.
  • OPAMBUILDTEST — Removed in 2.1. also dead 💀
  • OPAMCLI — see option --cli.
  • OPAMCOLOR — when set to always or never, sets a default value for the --color option.
  • OPAMCONFIRMLEVEL — see option --confirm-level. Heads up: OPAMCONFIRMLEVEL has priority over OPAMYES and OPAMNO. 👑
  • OPAMCRITERIA — specifies user preferences for dependency solving. The default value depends on the solver version, so run config report to know the current setting. See also option --criteria.
  • OPAMCUDFFILE — save the cudf graph to file-actions-explicit.dot.
  • OPAMCUDFTRIM — controls the filtering of unrelated packages during CUDF preprocessing.
  • OPAMCURL — can be used to select a given 'curl' program. See OPAMFETCH for more options.
  • OPAMDEBUG — see options --debug and --debug-level.
  • OPAMDEBUGSECTIONS — if set, limits debug messages to the space-separated list of sections. Sections can optionally have a specific debug level (for example, CLIENT:2 or CLIENT CUDF:2), but otherwise use --debug-level.
  • OPAMDIGDEPTH — defines how aggressive the lookup for conflicts during CUDF preprocessing is.
  • OPAMDOWNLOADJOBS — sets the maximum number of simultaneous downloads.
  • OPAMDROPWORKINGDIR — overrides packages previously updated with --working-dir on update. Without this variable set, opam would keep them unchanged unless explicitly named on the command-line.
  • OPAMDRYRUN — see option --dry-run.
  • OPAMEDITOR — sets the editor to use for opam file editing, overrides $EDITOR and $VISUAL. slay, it truly said "I'm the main character here" 💅
  • OPAMERRLOGLEN — sets the number of log lines printed when a sub-process fails. 0 to print all.
  • OPAMEXTERNALSOLVER — see option --solver.
  • OPAMFAKE — see option --fake.
  • OPAMFETCH — specifies how to download files: either wget, curl or a custom command where variables %{url}%, %{out}%, %{retry}%, %{compress}% and %{checksum}% will be replaced. Overrides the 'download-command' value from the main config file.
  • OPAMFIXUPCRITERIA — same as OPAMUPGRADECRITERIA, but specific to fixup and reinstall.
  • OPAMIGNOREAVAILABLE — see install option --ignore-available-on.
  • OPAMIGNORECONSTRAINTS — see install option --ignore-constraints-on.
  • OPAMIGNOREPINDEPENDS — see option --ignore-pin-depends.
  • OPAMINPLACEBUILD — see option --inplace-build.
  • OPAMJOBS — sets the maximum number of parallel workers to run.
  • OPAMJSON — log json output to the given file (use character % to index the files).
  • OPAMKEEPBUILDDIR — see install option --keep-build-dir.
  • OPAMKEEPLOGS — tells opam to not remove some temporary command logs and some backups. This skips some finalisers and may also help to get more reliable backtraces.
  • OPAMLOCKED — combination of --locked and --lock-suffix options.
  • OPAMLOGS — logdir sets log directory, default is a temporary directory in /tmp.
  • OPAMMAKECMD — set the system make command to use.
  • OPAMMERGEOUT — merge process outputs, stderr on stdout.
  • OPAMNO — answer no to any question asked, see options --no and --confirm-level. OPAMNO is ignored if either OPAMCONFIRMLEVEL or OPAMYES is set.
  • OPAMNOAGGREGATE — with opam admin check, don't aggregate packages.
  • OPAMNOASPCUD — Deprecated. 🚩
  • OPAMNOAUTOUPGRADE — disables automatic internal upgrade of repositories in an earlier format to the current one, on 'update' or 'init'.
  • OPAMNOCHECKSUMS — enables option --no-checksums when available.
  • OPAMNODEPEXTS — disables system dependencies handling, see option --no-depexts.
  • OPAMNOENVNOTICE — Internal.
  • OPAMNOSELFUPGRADE — see option --no-self-upgrade.
  • OPAMPINKINDAUTO — sets whether version control systems should be detected when pinning to a local path. Enabled by default since 1.3.0.
  • OPAMPRECISETRACKING — fine grain tracking of directories.
  • OPAMPREPRO — set this to false to disable CUDF preprocessing. Less efficient, but might help debugging solver issue.
  • OPAMREPOSITORYTARRING — internally store all non-vcs repositories as tar.gz files (by default, http repositories are stored as archive). This can be much faster on filesystems that don't cope well with scanning large trees. All operation are done in-memory, no I/O for scanning the repository.
  • OPAMREQUIRECHECKSUMS — Enables option --require-checksums when available (e.g. for opam install).
  • OPAMRETRIES — sets the number of tries before failing downloads.
  • OPAMREUSEBUILDDIR — see option --reuse-build-dir.
  • OPAMROOT — see option --root. This is automatically set by opam env --root=DIR --set-root.
  • OPAMROOTISOK — don't complain when running as root. 😌
  • OPAMSAFE — see option --safe.
  • OPAMSHOW — see option --show.
  • OPAMSKIPUPDATE — see option --skip-updates.
  • OPAMSKIPVERSIONCHECKS — bypasses some version checks. ⚠️ Unsafe, for compatibility testing only.
  • OPAMSOLVERALLOWSUBOPTIMAL — (default true) allows some solvers to still return a solution when they reach timeout; while the solution remains assured to be consistent, there is no guarantee in this case that it fits the expected optimisation criteria. If true, opam will continue with a warning, if false a timeout is an error. Currently only the builtin-z3 backend handles this degraded case.
  • OPAMSOLVERTIMEOUT — change the time allowance of the solver. Default is 60.0, set to 0 for unlimited. Note that all solvers may not support this option.
  • OPAMSOLVERTOLERANCE — changes the tolerance towards the solver choosing an unoptimized solution (i.e. might pull outdated packages). Typical values range from 0.0 (best solution known to the solver) to 1.0 (unoptimized solution). Default is 0.0. This option is useful in case the solver can't find a solution in a reasonable time (see $OPAMSOLVERTIMEOUT). Note that all solvers may not support this option.
  • OPAMSTATS — Removed in 2.4. 💀
  • OPAMSTATUSLINE — display a dynamic status line showing what's currently going on on the terminal. (one of always, never or auto)
  • OPAMSTRICT — fail on inconsistencies (file reading, switch import, etc.).
  • OPAMSWITCH — see option --switch. Automatically set by opam env --switch=SWITCH --set-switch.
  • OPAMUNLOCKBASE — see install option --unlock-base.
  • OPAMUPGRADECRITERIA — specifies user preferences for dependency solving when performing an upgrade. Overrides OPAMCRITERIA in upgrades if both are set. See also option --criteria.
  • OPAMUSEINTERNALSOLVER — see option --use-internal-solver.
  • OPAMUSEOPENSSL — Removed in 2.2. 💀
  • OPAMUTF8 — use UTF8 characters in output (one of always, never or auto). By default auto, which is determined from the locale).
  • OPAMUTF8MSGS — use extended UTF8 characters (camels) in opam messages. 🐪 Implies OPAMUTF8. This is set by default on macOS only.
  • OPAMVALIDATIONHOOK — if set, uses the %{hook}% command to validate an opam repository update.
  • OPAMVERBOSE — see option --verbose.
  • OPAMVERBOSEON — see option --verbose-on.
  • OPAMVERSIONLAGPOWER — do not use. 🙅 that's it, that's the whole instruction, do not use.
  • OPAMWITHDEVSETUP — see install option --with-dev-setup.
  • OPAMWITHDOC — see install option --with-doc.
  • OPAMWITHTEST — see install option --with-test.
  • OPAMWORKINGDIR — see option --working-dir.
  • OPAMYES — see options --yes and --confirm-level. OPAMYES has priority over OPAMNO and is ignored if OPAMCONFIRMLEVEL is set.
  • OPAMVAR_var — overrides the contents of the variable var when substituting %{var}% strings in opam files.
  • OPAMVAR_package_var — overrides the contents of the variable package:var when substituting %{package:var}% strings in opam files.

🕰️ CLI VERSION 🕰️

ok so this one is the "future-proof yourself" section and honestly it's giving responsibly slay ✨

All scripts and programmatic invocations of opam should use --cli in order to ensure that they work seamlessly with future versions of the opam client. Plus — and this is the cute part — blog posts or other documentation can benefit, as it prevents information from becoming stale. no more dusty tutorials, bestie 🎀

Although opam only supports roots (~/.opam/) for the current version, it does provide backwards compatibility for its command-line interface.

Since CLI version support was only added in opam 2.1, use OPAMCLI to select 2.0 support (as opam 2.0 will just ignore it), and --cli=2.1 for 2.1 (or later) versions, since an environment variable controlling the parsing of syntax is brittle. To this end, opam displays a warning if OPAMCLI specifies a valid version other than 2.0, and also if --cli=2.0 is specified. 👀

The command-line version is selected by using the --cli option or the OPAMCLI environment variable. --cli may be specified more than once, where the last instance takes precedence. OPAMCLI is only inspected if --cli is not given.

💀 EXIT STATUS

Okay bestie, listen — opam tells you exactly why it's mad at you, in numbers. Here's the decoder ring 🎀

🌟 One big exception to everything below: the exec command returns 127 if the command wasn't found or couldn't be executed, and otherwise it returns the command's own exit value. So like, opam exec hands you the vibes of the thing it ran. iykyk.
  • 0 — Success! Or "true" for boolean queries. We love a green flag 💚
  • 1 — False. This one shows up when a boolean return value is expected, like when you run with --check, or for queries like opam lint.
  • 2 — Bad command-line arguments, or arguments that point at an invalid context (e.g. a file that isn't in the expected format). Basically: bestie, that's not a thing.
  • 5 — Not found. You asked for something (package, version, repository, etc.) and it simply does not exist. Ghosted, fr fr 👻
  • 10 — Aborted. The operation needed confirmation and you didn't give it. No consent, no command 😭
  • 15 — Could not acquire the locks required for the operation. Something else is holding the door 🔒
  • 20 — There is no solution to the user request. Classic cause: asking to install two incompatible packages at once. Pick a lane, babe ✋
  • 30 — Error in package definition, or in other metadata files. Heads up: using --strict raises this error more often.
  • 31 — Package script error. Some package operations were unsuccessful. Might be an error in the packages, might be an incompatibility with your system. This can be a partial error.
  • 40 — Sync error. Couldn't fetch some remotes from the network. This can be a partial error too.
  • 50 — Configuration error. Opam or your system config doesn't allow the operation, and it needs fixing.
  • 60 — Solver failure. The solver failed to return a sound answer. Could be a broken external solver, or an error in the solver configuration. The solver is going through it 🫠
  • 99 — Internal error. Something went wrong, likely due to a bug in opam itself. Not your fault, bestie.
  • 130 — User interrupt. SIGINT was received, generally because the user pressed Ctrl+C. You did this. It's fine. We've all done it 🙈

And then there's this lil' cluster, exactly as listed:

  • 0 — on success.
  • 123 — on indiscriminate errors reported on standard error.
  • 124 — on command line parsing errors.
  • 125 — on unexpected internal errors (bugs).

📚 FURTHER DOCUMENTATION

See https://opam.ocaml.org/doc. Go read it, it's giving ✨ scholarly ✨.

👑 AUTHORS

The absolute icons who built this. Put some respect on their names:

  • David Allsopp <david@tarides.com>
  • Vincent Bernardoff <vb@luminar.eu.org>
  • Raja Boujbel <raja.boujbel@ocamlpro.com>
  • Kate Deplaix <kit-ty-kate@exn.st>
  • Roberto Di Cosmo <roberto@dicosmo.org>
  • Thomas Gazagnaire <thomas@gazagnaire.org>
  • Louis Gesbert <louis.gesbert@ocamlpro.com>
  • Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
  • Anil Madhavapeddy <anil@recoil.org>
  • Guillem Rieu <guillem.rieu@ocamlpro.com>
  • Ralf Treinen <ralf.treinen@pps.jussieu.fr>
  • Frederic Tuong <tuong@users.gforge.inria.fr>

🌈 SEE ALSO

  • opam(1) — the main character. Go read that one too.

🐛 BUGS

Check bug reports at https://github.com/ocaml/opam/issues. Found a bug? Report it, don't just suffer in silence, bestie 🫶

And that's the whole page, babes!! 💖 This was Opam 2.6.1, served up as OPAM-SEARCH(1), and we are officially done. Now go search for some packages and slay ✨💅🎀

📦 where this page comes from