fix: move audio files to public directory for build inclusion #699
Conversation
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
|
@wo-o29 is attempting to deploy a commit to the Toss Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
📝 Key Changes
This PR fixes an issue where audio files referenced in the accessibility documentation were not being included in the build output, making them inaccessible to users.
a11y-audio.mp3referenced in the accessibility guide was not being included in the VitePress build output, resulting in a 404 error when users tried to play the audio example.audios/directory to the VitePresspublic/directory and updated the reference path to use an absolute path. This ensures that audio files are properly copied to the build output and accessible at runtime.🖼️ Before and After Comparison