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

Won't be able to use kpm on react-native/at fb yet #37

Closed
vjeux opened this issue Feb 4, 2016 · 2 comments
Closed

Won't be able to use kpm on react-native/at fb yet #37

vjeux opened this issue Feb 4, 2016 · 2 comments

Comments

@vjeux
Copy link
Contributor

vjeux commented Feb 4, 2016

So, as I suspected, you are using symlinks for generating all those node_modules. Unfortunately, watchman doesn't support symlinks. This has been a longstanding issue (can't use npm link) and we need to figure out a solution with the watchman team.

@sebmck
Copy link
Contributor

sebmck commented Feb 5, 2016

Why does watchman need to watch the dependencies?

On Thu, Feb 4, 2016 at 9:06 PM, Christopher Chedeau
notifications@github.com wrote:

So, as I suspected, you are using symlinks for generating all those node_modules. Unfortunately, watchman doesn't support symlinks. This has been a longstanding issue (can't use npm link) and we need to figure out a solution with the watchman team.

Reply to this email directly or view it on GitHub:
#37

@sebmck
Copy link
Contributor

sebmck commented Feb 5, 2016

Just had a talk with @shayne. This is likely because the RNP uses watchman to get fast file lookup for dependency resolution. We can likely bypass watchman all together and offer something even faster via kpm if this is the only use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants