Repository navigation
fix: keep astro check out of dist after a local build - #735
Merged
Merged
Conversation
Contributor
Author
|
lgtm |
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
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.
A second
npm run buildin the same checkout fails:astro checktype-checks the bundled JavaScript indist/left by the first build and aborts. CI never sees it because it builds from a clean checkout, so it only bites locally, and the workaround is deletingdist/before every build.The cause is
tsconfig.json'sexclude. Astro's base tsconfig excludesdist, but settingexcludehere replaces that list instead of adding to it, sodistwas no longer excluded oncefunctionswas. This putsdistback next tofunctions.Checked by building with a stale
dist/present:astro checkreports 0 errors and the build completes.