`custom` spawns a child process of your shell, so it's probably being slowed down by a slow shell init script.
If the custom script you're running doesn't require your full shell customization to work, you can provide a custom shell command [0], passing an argument to not use your shell config.
For instance: `fish --no-config` or `bash --noprofile --norc`
Starship can be quickly configured to have a select few "modules" enabled. This can be configured with `prompt_order`, documented here: https://starship.rs/config/#prompt
I, for one, like to know what version of Node will be used when I'm jumping between projects, so I can know which features are available to me at runtime.
Eventually we'd like to include an interactive configuration tool to help folks find a configuration that meets their needs.
`custom` spawns a child process of your shell, so it's probably being slowed down by a slow shell init script. If the custom script you're running doesn't require your full shell customization to work, you can provide a custom shell command [0], passing an argument to not use your shell config. For instance: `fish --no-config` or `bash --noprofile --norc`
[0]: https://starship.rs/config/#custom-command-shell