detect 11ty's output dir as staticDistDir
#895
Merged
Conversation
This file contains 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
paulirish
approved these changes
Apr 13, 2023
paulirish
changed the title
staticDistDirstaticDistDir
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hey 👋🏻
I was surprised when Lighthouse CI didn't detect my built page when setting up a new build. The error message was really helpful, so I got up and running quickly, but I figured I'd ask if you'd consider adding
_siteto the list of automatically detectstaticDistDirdirectories.I figured that it would be a low-risk change, since I suspect that there aren't many directories named
_sitein other systems.Let me know what you think :)
References
https://www.11ty.dev/docs/config/#output-directory