There's ASDF [0] and Quicklisp [1], but nothing so rigid as NPM. It's more like the old C configuration, when you install stuff with a package manager or download DLL and headers. But Lips is not like JavaScript or Rust where you code, then you compile/build and have a program. It's more like an OS that you boot and then interact with it, adding code and data. Quicklisp is more akin to a package manager than a dependency system and ASDF is more like Ansible. The Lisp code you write are equivalent to shell script to get the program to a particular state. You can save an image of the program somewhere so you don't have to reload everything from scratch and then your code is more like a documentation at this point.

My whole workflow with Common Lisp is playing around with the interpreter in search of a solution, then write down that solution in code. Quicklisp is more than enough for that. If I need to pin down a library, I'd just download it and vendor it in the project. And most people don't need that much libraries as the language is quite flexible and you can get it very close to the problem domain.

> What I want is a lisp with a compiler/interpreter, and a package manager/build system that makes use of said compiler/interpreter to work on a project using a standardized project structure.

What you're asking is the same as Docker for Linux, but if Linux was more homogeneous and running a single program. Docker wouldn't be so useful and people would just distribute VM snapshots or Ansible scripts. Which you do in Lisp.

[0]: https://asdf.common-lisp.dev/

[1]: https://www.quicklisp.org/beta/