Document new getViteConfig() option for Vitest#8192
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
Contributor
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
sarah11918
reviewed
May 6, 2024
delucis
commented
May 7, 2024
sarah11918
approved these changes
May 8, 2024
Member
sarah11918
left a comment
There was a problem hiding this comment.
Looks great, thanks @delucis !
Member
|
updating branch and pointing to 4.8.0 branch! |
sarah11918
reviewed
May 8, 2024
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.
Description (required)
Updates the Vitest testing docs to mention a new config option.
For Astro version:
4.8. See astro PR withastro/astro#10963.I did not use
<Since />in this case because it doesn’t really work well inline in the way I integrated these new docs. Any thoughts on whether this should be added somehow? There could be a separate heading to fit it under, but that felt a little artificial.