test: add browser mode tests for nuxt/content components #1284
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
commit: |
JessicaSachs
force-pushed
the
jess/vitest-nuxt-content
branch
from
480ca9d to
2c41fd6
Compare
danielroe
changed the title
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
🔗 Linked issue
#1283
TODO
❓ Type of change
📚 Description
The Nuxt Content module relies on
useRuntimeConfigin order to render any of its built-in ProseH1, ProseH2, or ProseH3 components. Currently, components that calluseRuntimeConfigwithin setup throw an error that the Nuxt instance is not available.This only happens in browser mode.
Running the Tests
To execute the tests, you can run:
I've marked the failing tests as "skipped"