build(sveltekit): Remove vite types from build output#7480
Merged
Conversation
Contributor
size-limit report 📦
|
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.
In #7438, we added
vite.config.tsto our SvelteKit pacakge. We also added it to oursveltekit/tsconfig.jsoninstead ofsveltekit/tsconfig.test.jsonwhich meant that some types from Vite ended up in oursveltekt/build/typesdirectory.This messed up the directory structure and causing the types entry point to no longer be valid. This PR fixes that by adding the vite config totsconfig.test.json.Also, this PR fixes the
test:unityarn script as just executingviteststarted vitest in watch mode on local machines (and single-run mode on CI). IMO we shouldn't start it in watch mode by default, as we havetest:unit:watchto do that.