elpaca

> In the meantime we're all stuck waiting for package downloads. I use Elpaca instead of the built-in package manager, which is better designed (declarative package specification) and fully asynchronous. The UI is also more thoughtful, with more granular search-as-you-type capability and easy git commit reviews of pending package updates. package.el is catching up to Elpaca in features, but async installs/updates is not one of them. https://github.com/progfolio/elpaca

I second this, although i use `elpaca with use-package` instead: https://github.com/progfolio/elpaca It helps me keep the config consistent regardless of if something comes from MELPA, or bitbucket/github/gitlab etc. - I also keep my config in README.org an github which shows the preview by default - Org mode also helps me keep the commentary alongside. I can even just mark stuff as TODO, COMMENT with keyboard shortcuts. Infact if you read the source instead you'll find parts with COMMENT that don't render in the default preview on browser on Github. - The git + github bits ofcourse help me use branches/PRs where i can test out stuff. Eg. most recently i was trying out lsp-bridge over eglot. Here's my literate config: https://github.com/sidmitra/emacs.d PS: Over time some bits have moved back to init.el to take precedence rather than ever

Elpaca [1] does not do this. I use it and it works a treat. 1: https://github.com/progfolio/elpaca

Just an fyi for people using straight or interested in it, its maintainer is working on an alternative called elpaca. https://github.com/progfolio/elpaca