Use this tag for questions regarding janet's package manager.
Most default installs of Janet come with a build tool, jpm, that makes managing dependencies, building Janet code, and distributing Janet applications easy. While jpm is not required by Janet, it is a very handy build tool that removes much of the boilerplate for creating new Janet projects, and is updated in step with Janet. jpm also works on Windows, Linux, and macOS so you don't need to write multiple build scripts and worry about platform quirks to make your scripts, binaries, and applications cross-platform.
jpm's main functions are installing dependencies and building native Janet modules, but it is meant to be used for much of the life-cycle for Janet projects. Since Janet code doesn't usually need to be compiled, you don't always need jpm, especially for scripts, but jpm comes with some functionality that is difficult to duplicate, like compiling Janet source code and all imported modules into a statically linked executable for distribution.
