docs: update startup stages to include sourcing of autoload directories#2158
Merged
fdncred merged 1 commit intonushell:mainfrom Apr 21, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR updates the scenarios to describe when the files in
vendor-autoload-dirsand the files inuser-autoload-dirsare loaded.vendor-autoload-dirsanduser-autoload-dirsare loaded only whensetup_config()is executed. That occurs for regular REPL startup and for LSP/MCP startup when config files are allowed. In contrast, command-string execution (nu -c ...) and script execution (nu script.nu) userun_commands()andrun_file(), which do not callsetup_config(), so autoload directories are not processed in those cases.