docs: mention module resolution differences for package managers #9665
+8
−0
Conversation
This file contains 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
turbo-orchestrator
bot
added
the
area: docs
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
anthonyshew
changed the title
chris-olszewski
approved these changes
Jan 2, 2025
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
We've gotten reports before about the documentation being wrong when it's actually an issue with a package manager behaving in a bizarre way or a specific setting for a package manager not working with the strategy proposed in the documentation.
We won't be able to document every edge case or odd behavior of every package manager's module resolution algorithm, so I'd prefer to make mention of this in the docs.
We do our best. 😬
Testing Instructions
👀