docs: document ssr.resolve.conditions for custom package conditions
#9392
+47
−0
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
…onditions Co-authored-by: hi-ogawa <[email protected]>
…onsistent defaults Co-authored-by: hi-ogawa <[email protected]>
✅ Deploy Preview for vitest-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Copilot
AI
changed the title
[WIP] Propose documentation changes for issue 9391
docs: document ssr.resolve.conditions for subpath imports with custom conditions
Jan 5, 2026
sheremet-va
requested changes
Jan 5, 2026
docs/guide/common-errors.md
Outdated
| ::: tip Why `ssr.resolve.conditions` and not `resolve.conditions`? | ||
| Vitest inherits Vite's configuration convention where: | ||
| - `resolve.conditions` is used for client-side application code (browser environments) | ||
| - `ssr.resolve.conditions` is used for server-side application code (Node.js environments) |
Member
There was a problem hiding this comment.
This is incorrect, transform mode is based on the environment (jsdom/happy-dom use resolve.conditions), custom environments can define transformMode property
Contributor
Author
There was a problem hiding this comment.
Fixed in b21497b - clarified that transform mode is based on the environment (jsdom/happy-dom use resolve.conditions, node uses ssr.resolve.conditions), and custom environments can define transformMode property.
hi-ogawa
changed the title
ssr.resolve.conditions for custom conditions
hi-ogawa
reviewed
Jan 7, 2026
docs/guide/common-errors.md
Outdated
| ``` | ||
| ::: | ||
|
|
||
| ## Subpath imports with custom conditions are not resolved |
Contributor
Contributor
Author
…ode behavior Co-authored-by: hi-ogawa <[email protected]>
✅ Deploy Preview for vitest-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Copilot
AI
changed the title
docs: document
docs: document Jan 7, 2026
ssr.resolve.conditions for custom conditionsssr.resolve.conditions for custom package conditions
hi-ogawa
approved these changes
Jan 7, 2026
sheremet-va
requested changes
Jan 7, 2026
- Clarify Vite environment configuration convention - Fix viteEnvironment value from 'web' to 'client' - Add reference to environment config documentation 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
sheremet-va
approved these changes
Jan 8, 2026
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.
Related
Users cannot resolve package exports or subpath imports with custom conditions in Vitest because
ssr.resolve.conditionsconfiguration is undocumented, leading to confusion about whyresolve.conditionsdoesn't work.Changes
docs/guide/common-errors.mdssr.resolve.conditionsconfigurationresolve.conditionsfor browser-like environments (jsdom, happy-dom, or custom environments withtransformMode: 'web'), andssr.resolve.conditionsfor Node-like environments (node, or custom environments withtransformMode: 'ssr')Example
This works for both package exports and subpath imports. By default, Vitest uses the
nodeenvironment which hastransformMode: 'ssr', so it usesssr.resolve.conditionsfor module resolution.✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.