Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SYNC] docs: dependency resolution warning, closes #4089 (#4197) #50

Closed
github-actions bot opened this issue Aug 26, 2021 · 0 comments · Fixed by #56
Closed

[SYNC] docs: dependency resolution warning, closes #4089 (#4197) #50

github-actions bot opened this issue Aug 26, 2021 · 0 comments · Fixed by #56
Labels

Comments

@github-actions
Copy link
Contributor

docs: dependency resolution warning, closes #4089 (#4197) (4c7af0a)


+++ b/docs/guide/dep-pre-bundling.md
@@ -38,6 +38,11 @@ After the server has already started, if a new dependency import is encountered
In a monorepo setup, a dependency may be a linked package from the same repo. Vite automatically detects dependencies that are not resolved from `node_modules` and treats the linked dep as source code. It will not attempt to bundle the linked dep, and instead will analyze the linked dep's dependency list instead.
+::: warning Note
+Linked dependencies might not work properly in the final build due to differences in dependency resolution.
+Use `npm package` instead for all local dependencies to avoid issues in the final bundle.
+:::
+
## Customizing the Behavior
The default dependency discovery heuristics may not always be desirable. In cases where you want to explicitly include/exclude dependencies from the list, use the [`optimizeDeps` config options](/config/#dep-optimization-options).
@github-actions github-actions bot added the sync label Aug 26, 2021
@Gumball12 Gumball12 mentioned this issue Sep 6, 2021
Gumball12 added a commit that referenced this issue Feb 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

0 participants