zsh-defer VS zsh-autoenv

zsh-defer

1.) It's fast. Like, really fast. 1.) It supports deferred loading via zsh-defer 1.) It supports local plugins as well as ones hosted via a git provider (aka: GitHub, GitLab, BitBucket, etc) 1.) The codebase is simple and easy to understand and contribute to 1.) It supports git branches (with tag/shas on the roadmap) 1.) It supports partial plugin loading such as loading Oh-My-Zsh plugins and Prezto modules without loading the whole framework. 1.) There's an easy migration path from legacy plugin managers like Antigen/Antibody. 1.) Plugins are managed via a simple plugins file that makes it easy to share your config with others. 1.) And lots more

I've recently sped up my startup by using zsh-defer which has worked very well. I think nvm (the variant loaded through zsh) also has an option to load asynchronously without something like zsh-defer

I use zsh-defer for lazy plugin loading and I fork all plugin repos to avoid the same situation as with zinit

You can use this as a plugin for deferred loading like zinit: https://github.com/romkatv/zsh-defer

Another one that I like: https://github.com/Tarrasch/zsh-autoenv

Can I ask if you're using zsh-autoenv or rtx or something else to achieve that?

For some of my projects I use zsh-autoenv for this.

I think zsh-autoenv does a great job handling this, as you describe:

But IMO the best solution by far is to use autoenv. There is autoenv for bash and autoenv for zsh.

zsh-autoenv

autoenv 🥇 - If a directory contains a .env file, it will automatically be executed when you cd into it.