-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Prioritize nodeModulesPath over config.root if present. #2507
Prioritize nodeModulesPath over config.root if present. #2507
Conversation
Faced the same issue with the wrong path to node_modules in monorepo setup after upgrading to react-native 0.72.3. Now |
TL;DR We have just upgraded to RN 0.72.3, and our project follows a monorepo setup too. While the PR isn't tested and merged, we will apply the patch as a workaround for now. -- We were about to reply in a related thread from the Issue Tracker, but we will share our struggles here instead. We are running We noticed that The approach worked fine while running
We were hoping to read android/app/build.gradle
codepush.gradle
We have attempted to override the |
Hello! I am having the same issue. Would it be possible to merge and deploy this? |
Anyone to merge this? |
1106295
to
7078150
Compare
Could you please pull our master branch into your branch? It fixed problems with tests. |
7078150
to
34165ef
Compare
Fixed 🙂 |
This has been discussed before in issue #1887 and in pull request #1943, but was closed because of inactivity.
Like mentioned in links, it would maybe be more natural to prioritize the direct
nodeModulesPath
property if present, not the reference to projects root.And with react native 0.71 new android config, I have seen that root is present even when not setting it in project. Which means
nodeModulesPath
is never used, which makes it useless in that case. Therefore taking up this change again, to switch the priority.