Remove proload for config loading #5778
Merged
+65
−162
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.
Changes
Close #5748
Fix #5459
resolveConfigPath
to only search for a config path, and not load the config itself, this fixes Issue withastro add
and@astrojs/mdx
#5459Note: I tried to use Vite's
loadConfigFromFile
instead, but it doesn't bring much benefit for us, and prevents named exports from the Astro config if we ever need it. It's also harder to test withcreateFs
sinceloadConfigFromFile
always read from the actual filesystem.Testing
Existing config loading test should work. Since this removes a proload feature, I don't think there's new test to add.
Docs
n/a. Ideally loading the config with Vite should always work, so this change shouldn't need a docs update.