Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Pack (alpha)

Package up Clojure projects in various ways, based on a deps.edn file.

Want to have a chat before opening a ticket? Need help or support from the community? Find us in the Clojurians Zulipchat #JUXT stream.



Pack provides the namespace juxt.pack.api which works well alongside Find reference documentation on the vars.

When using in a monorepo with multiple projects, it can be useful to leverage to specify the directory containing the deps.edn file for a particular project. Pack supports with-project-root by taking advantage of the included tools.deps library. Simply wrap all Pack calls with and pass the project root as the first argument.

(ns build
  (:require [ :as jio]
            [ :as b]
            [ :as t]
            [juxt.pack.api :as pack]))

(defn pack
 (b/with-project-root "path/to/project/root"
  (t/with-dir (jio/file b/*project-root*)

Note that the project root is passed as a Java file via

As a tool

Pack also works standalone as a tool you can invoke with deps.edn. Add this alias to your project:

;; add this to :aliases:
:pack {:deps {io.github.juxt/pack.alpha {:git/sha "843475881c5b3ba1a2c9f102f6f5f86f3293a574"}}
       :ns-default juxt.pack.cli.api}

Then you can invoke it with clj -T:pack. To see usage information, use clojure -A:deps -T:pack help/dir


Pack provides fast, conflict-less, ways to package Clojure programs. It provides:

  • Docker images

  • AWS Lambda deployment package

  • Self-executable jars (Using One-JAR)

  • "Skinny" jars (Jars which do not contain their dependencies)

  • Library jars

What does conflict-less mean?

Pack will always package your application so you don’t need to worry about multiple copies of the same file on the classpath. Pack preserves the classpath for all of it’s output formats.

Uberjars require that files on the classpath are uniquely named. To do this, they have to resolve conflicts between files with the same name. For example, if you two dependencies com.example/A and com.example/B, and both contain the file "data_readers.clj" in them, what do you do? Often configuration is needed to get this right, as many libraries aren’t supported out of the box. Some tools will even ignore copyright restrictions that require you to keep them in your final jar as a convenience.


PR your project here!


PR your guide here!


Package clojure projects







No releases published


No packages published