watchman - react native watchmanResponse unable to resolve root -


there error when build react-native project version 0.20.0:

looking js files in    /users/rockyl/workspaces/react-native/tinysns   [13:55:06] <start> building dependency graph [13:55:06] <start> crawling file system [13:55:06] <start> loading bundles layout [13:55:06] <end>   loading bundles layout (1ms) [hot module replacement] server listening on /hot  react packager ready.   error  unable resolve root /users/rockyl/workspaces/react-native/tinysns: failed opendir(/users/rockyl/workspaces/react-native/tinysns): no such file or directory {"watchmanresponse":{"version":"4.4.0","error":"unable resolve root /users/rockyl/workspaces/react-native/tinysns: failed opendir(/users/rockyl/workspaces/react-native/tinysns): no such file or directory"}} error: unable resolve root /users/rockyl/workspaces/react-native/tinysns: failed opendir(/users/rockyl/workspaces/react-native/tinysns): no such file or directory     @ bunserbuf.<anonymous> (/users/rockyl/workspaces/react-native/tinysns/node_modules/react-native/node_modules/sane/node_modules/fb-watchman/index.js:95:23)     @ emitone (events.js:77:13)     @ bunserbuf.emit (events.js:169:7)     @ bunserbuf.process (/users/rockyl/workspaces/react-native/tinysns/node_modules/react-native/node_modules/bser/index.js:289:10)     @ /users/rockyl/workspaces/react-native/tinysns/node_modules/react-native/node_modules/bser/index.js:244:12     @ dontcallback0 (node.js:419:9)     @ process._tickcallback (node.js:348:13)  see http://facebook.github.io/react-native/docs/troubleshooting.html common problems , solutions. 

here logs: watchman logs , here real-time logs: watchman real-time logs

but root path exists.

thanks posting logs; what's happening here issue casing of workspaces directory in path being watched. there's complicated background results in watchman needing know exact casing of file names can report on case-change-only-renames.

the tl;dr should either ask react native watch path using workspaces directory name, or rename directory workspaces (in other words, make sure path you're asking matches of filesystem).

there couple of watchman bugs here i'll work on fixing in meantime:

  1. we should canonicalize path using our strict canon @ earlier stage in watching (should make use case "just work")
  2. we should surface error explanation when such mismatch occurs

Comments

Popular posts from this blog

c# - How Configure Devart dotConnect for SQLite Code First? -

c++ - Clear the memory after returning a vector in a function -

erlang - Saving a digraph to mnesia is hindered because of its side-effects -