aranja/rakning-c19-app

Yarn install failure in Windows 10

yittoo opened this issue · 3 comments

Node Version: 12.13.1
Yarn Version: 1.19.1

System Information:
Windows 10 Pro 64bit
Intel i5 9400f
RTX 2060

Edit: If necessary I can help building Docker image for Android side development on Windows.

Log:

[1/4] Resolving packages...
[2/4] Fetching packages...
info fsevents@1.2.12: The platform "win32" is incompatible with this module.
info "fsevents@1.2.12" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " > eslint-import-resolver-babel-module@5.0.1" has unmet peer dependency "babel-plugin-module-resolver@^3.0.0".
warning " > eslint-plugin-jsx-a11y@6.2.0" has incorrect peer dependency "eslint@^3 || ^4 || ^5".
warning " > eslint-plugin-react@7.12.4" has incorrect peer dependency "eslint@^3.0.0 || ^4.0.0 || ^5.0.0".
warning "react-native-country-picker-modal > modal-react-native-web@0.2.0" has unmet peer dependency "react-art@16.x.x".
warning "react-native-country-picker-modal > modal-react-native-web@0.2.0" has incorrect peer dependency "react-native-web@0.9.x".
warning "react-navigation > react-navigation-drawer@1.4.0" has incorrect peer dependency "react-native-screens@^1.0.0 || ^1.0.0-alpha".
warning "react-navigation > react-navigation-stack@1.5.3" has incorrect peer dependency "react-native-screens@^1.0.0 || ^1.0.0-alpha".
warning "react-navigation > react-navigation-tabs@1.2.0" has incorrect peer dependency "react-native-screens@^1.0.0 || ^1.0.0-alpha".
[4/4] Building fresh packages...
[1/4] ⡀ core-js                                                                                                         [2/4] ⡀ postinstall-postinstall                                                                                         [3/4] ⡀ react-native-unimodules                                                                                         error D:\codingPlayground\rakning-c19-app\node_modules\postinstall-postinstall: Command failed.
Exit code: 1
Command: node ./run.js
Arguments:
Directory: D:\codingPlayground\rakning-c19-app\node_modules\postinstall-postinstall
Output:
**ERROR** Failed to apply patch for package @mauron85/react-native-background-geolocation

  This happened because the patch file patches\@mauron85+react-native-background-geolocation+0.6.3.patch could not be parsed.

  If you just upgraded patch-package, you can try running:

    cd patches\@mauron85+react-native-background-geolocation+0.6.3.patc
    patch -p1 -i h
    npx patch-package @mauron85/react-native-background-geolocation
    cd ../..

  Otherwise, try manually creating the patch file again.

  If the problem persists, please submit a bug report:

    https://github.com/ds300/patch-package/issues/new?title=Patch+file+parse+error&body=%3CPlease+attach+the+patch+file+in+question%3E


error Command failed with exit code 1.
child_process.js:660
    throw err;
    ^

Error: Command failed: yarn run postinstall

**ERROR** Failed to apply patch for package @mauron85/react-native-background-geolocation

  This happened because the patch file patches\@mauron85+react-native-background-geolocation+0.6.3.patch could not be parsed.

  If you just upgraded patch-package, you can try running:

    cd patches\@mauron85+react-native-background-geolocation+0.6.3.patc
    patch -p1 -i h
    npx patch-package @mauron85/react-native-background-geolocation
    cd ../..

  Otherwise, try manually creating the patch file again.

  If the problem persists, please submit a bug report:

    https://github.com/ds300/patch-package/issues/new?title=Patch+file+parse+error&body=%3CPlease+attach+the+patch+file+in+question%3E


error Command failed with exit code 1.

    at checkExecSyncError (child_process.js:621:11)
    at execSync (child_process.js:657:15)
    at Object.<anonymous> (D:\codingPlayground\rakning-c19-app\node_modules\postinstall-postinstall\run.js:14:5)
    at Module._compile (internal/modules/cjs/loader.js:959:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
    at Module.load (internal/modules/cjs/loader.js:815:32)
    at Function.Module._load (internal/modules/cjs/loader.js:727:14)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10)
    at internal/main/run_main_module.js:17:11 {
  status: 1,
  signal: null,
  output: [
    null,
    <Buffer 79 61 72 6e 20 72 75 6e 20 76 31 2e 31 39 2e 31 0a 24 20 70 61 74 63 68 2d 70 61 63 6b 61 67 65 0a 70 61 74 63 68 2d 70 61 63 6b 61 67 65 20 36 2e 32 ... 108 more bytes>,
    <Buffer 0a 2a 2a 45 52 52 4f 52 2a 2a 20 46 61 69 6c 65 64 20 74 6f 20 61 70 70 6c 79 20 70 61 74 63 68 20 66 6f 72 20 70 61 63 6b 61 67 65 20 40 6d 61 75 72 ... 709 more bytes>
  ],
  pid: 3576,
  stdout: <Buffer 79 61 72 6e 20 72 75 6e 20 76 31 2e 31 39 2e 31 0a 24 20 70 61 74 63 68 2d 70 61 63 6b 61 67 65 0a 70 61 74 63 68 2d 70 61 63 6b 61 67 65 20 36 2e 32 ... 108 more bytes>,
  stderr: <Buffer 0a 2a 2a 45 52 52 4f 52 2a 2a 20 46 61 69 6c 65 64 20 74 6f 20 61 70 70 6c 79 20 70 61 74 63 68 20 66

This is super weird. Does patch-package not work on Windows? Or is our patch file not compatible somehow? Line endings??

Our patch file was generated by patch-package, so I assume it's an upstream issue.

Looks like this issue: ds300/patch-package#207

maybe ds300/patch-package#301 could resolve this issue .