We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Do you want to request a feature or report a bug?
bug 🐛
What is the current behavior?
Module resolution fails when dependency is installed using PNPM, because symlinks are heavily utilized.
(only tested with the Watchman crawler)
If the current behavior is a bug, please provide the steps to reproduce and a minimal repository on GitHub that we can yarn install and yarn test.
yarn install
yarn test
Link to repro
What is the expected behavior?
Metro should be aware of symlinks in node_modules whose "real path" contains a package.json and use this information to resolve dependencies.
node_modules
package.json
Please provide your exact Metro configuration and mention your Metro, node, yarn/npm version and operating system.
metro v0.43.6
node v10.9.0
pnpm v2.13.5
macOS v10.13.6
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Do you want to request a feature or report a bug?
bug 🐛
What is the current behavior?
Module resolution fails when dependency is installed using PNPM, because symlinks are heavily utilized.
(only tested with the Watchman crawler)
If the current behavior is a bug, please provide the steps to reproduce and a minimal repository on GitHub that we can
yarn install
andyarn test
.Link to repro
What is the expected behavior?
Metro should be aware of symlinks in
node_modules
whose "real path" contains apackage.json
and use this information to resolve dependencies.Please provide your exact Metro configuration and mention your Metro, node, yarn/npm version and operating system.
metro v0.43.6
node v10.9.0
pnpm v2.13.5
macOS v10.13.6
The text was updated successfully, but these errors were encountered: