Errors running on windows in git bash: EPERM operation not permitted, could not find parent dir #18

klues · 2020-08-20T14:38:45Z

I get the following error on running npx yarn-audit-fix on windows in git bash:

npx yarn-audit-fix
Preparing temp assets...
Error: EPERM: operation not permitted, symlink '..\..' -> 'C:\data\src\<my project>\node_modules\.cache\yarn-audit-fix\node_modules'

running the same in a console with administrator privileges results in this error:

npx yarn-audit-fix
Preparing temp assets...
Generating package-lock.json from yarn.lock...
Error: Could not find parent dir!
    at parentPackagePath (C:\data\src\<my project>\node_modules\synp\util\traverse.js:9:11)
    at C:\data\src\<my project>\node_modules\synp\lib\lockfileV1\tree.js:67:30

thanks for any hints to get it running.

The text was updated successfully, but these errors were encountered:

antongolub · 2020-08-20T20:11:45Z

Hi @klues

There're some issues with synp and yarn-audit-fix we're trying to solve right now (imsnif/synp#46). Could you try out the latest 2.0.0-rc.5?

npx yarn-audit-fix@2.0.0-rc.5 --package-lock-only

UPD
I'd also recommend to pass --symlink=junction flag to bypass the permission restrictions.

MattSwartz · 2020-08-20T20:44:48Z

Same thing here. I did try the 2.0.0-rc.5 with the same results. See below

$ npx yarn-audit-fix@2.0.0-rc.5 --symlink=junction
npx: installed 375 in 11.943s
Preparing temp assets...
Generating package-lock.json from yarn.lock...
Error: Could not find parent dir!
    at parentPackagePath (C:\Users\matt\AppData\Roaming\npm-cache\_npx\33692\node_modules\yarn-audit-fix\node_modules\@antongolub\synp\util\traverse.js:9:11)
    at C:\Users\matt\AppData\Roaming\npm-cache\_npx\33692\node_modules\yarn-audit-fix\node_modules\@antongolub\synp\lib\lockfileV1\tree.js:65:30
    at Array.reduce (<anonymous>)
    at buildNpmTree (C:\Users\matt\AppData\Roaming\npm-cache\_npx\33692\node_modules\yarn-audit-fix\node_modules\@antongolub\synp\lib\lockfileV1\tree.js:51:8)
    at convertYarnToNpmV1 (C:\Users\matt\AppData\Roaming\npm-cache\_npx\33692\node_modules\yarn-audit-fix\node_modules\@antongolub\synp\lib\lockfileV1\index.js:13:26)
    at convertYarnToNpm (C:\Users\matt\AppData\Roaming\npm-cache\_npx\33692\node_modules\yarn-audit-fix\node_modules\@antongolub\synp\lib\index.js:15:9)
    at Object.yarnToNpm (C:\Users\matt\AppData\Roaming\npm-cache\_npx\33692\node_modules\yarn-audit-fix\node_modules\@antongolub\synp\index.js:15:12)
    at yarnLockToPkgLock (C:\Users\matt\AppData\Roaming\npm-cache\_npx\33692\node_modules\yarn-audit-fix\target\es5\index.js:90:42)
    at C:\Users\matt\AppData\Roaming\npm-cache\_npx\33692\node_modules\yarn-audit-fix\target\es5\index.js:179:21
    at step (C:\Users\matt\AppData\Roaming\npm-cache\_npx\33692\node_modules\yarn-audit-fix\target\es5\index.js:33:23)

Let me know what information I can supply to help.

antongolub · 2020-08-20T21:07:19Z

Oh... It seems to be all about path separators. Fixed imsnif/synp@5bfa495. Could you try 2.0.0-rc.7?

UPD I should add windows-based testing task

antongolub · 2020-08-20T23:19:14Z

@MattSwartz @klues

I've added windows os to build matrix. Everything seems to be ok.
https://travis-ci.com/github/antongolub/yarn-audit-fix/jobs/375950459

klues · 2020-08-21T06:05:37Z

thank you very much for the support!

I've tried rc7, this is the result:

npx yarn-audit-fix@2.0.0-rc.7 --symlink=junction
npx: Installierte 375 in 12.618s
Preparing temp assets...
Generating package-lock.json from yarn.lock...
Applying npm audit fix...
invoke node node_modules/npm/bin/npm-cli.js audit fix --prefix=C:\data\src\<my-project>\node_modules\.cache\yarn-audit-fix
internal/modules/cjs/loader.js:983
  throw err;
  ^

Error: Cannot find module 'C:\data\src\<my-project>\node_modules\.cache\yarn-audit-fix\node_modules\npm\bin\npm-cli.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:980:15)
    at Function.Module._load (internal/modules/cjs/loader.js:862:27)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
    at internal/main/run_main_module.js:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
{
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 11764,
  stdout: null,
  stderr: null
}

antongolub · 2020-08-21T06:32:51Z

@klues

I guess this is because npm audit fix is trying to eliminate the difference in the node_modules directory structure. Let's try this workaround:

Restore the original node_modules state. yarn --force or rm-rf node_modules && yarn.
Apply npx yarn-audit-fix@2.0.0-rc.7 --symlink=junction --package-lock-only. The last param should instruct npm not to modify node_modules contents.

klues · 2020-08-21T06:46:21Z

I did

rm -rf node_modules
rm -rf yarn.lock
yarn
npx yarn-audit-fix@2.0.0-rc.7 --symlink=junction --package-lock-only

but unfortunately it results in the same error.
Maybe this line is the problem:
invoke node node_modules/npm/bin/npm-cli.js audit fix --prefix=C:\data\src\<my-project>\node_modules\.cache\yarn-audit-fix
where the current node_modules\.cache directory is passed as --prefix?!

antongolub · 2020-08-21T07:10:05Z

@klues

Most likely you are right. I'll experiment with this a little later.

antongolub · 2020-08-21T10:50:25Z

@klues, @MattSwartz

I've added several tweak ups. Could you take a look at 2.0.0-rc.9 build?

klues · 2020-08-21T11:19:26Z

this is my result for rc.9:

npx yarn-audit-fix@2.0.0-rc.9 --symlink=junction --package-lock-only
npx: Installierte 375 in 13.941s
Preparing temp assets...
Generating package-lock.json from yarn.lock...
Applying npm audit fix...
invoke C:\Users\<user>\AppData\Roaming\npm-cache\_npx\18796\node_modules\yarn-audit-fix\node_modules\.bin\npm audit fix --package-lock-only --prefix=C:\data\src\<project>\node_modules\.cache\yarn-audit-fix
{
  error: Error: spawnSync C:\Users\<user>\AppData\Roaming\npm-cache\_npx\18796\node_modules\yarn-audit-fix\node_modules\.bin\npm ENOENT
      at Object.spawnSync (internal/child_process.js:1045:20)
      at Object.spawnSync (child_process.js:597:24)
      at Object.exports.invoke (C:\Users\<user>\AppData\Roaming\npm-cache\_npx\18796\node_modules\yarn-audit-fix\target\es5\util.js:23:42)
      at npmAuditFix (C:\Users\<user>\AppData\Roaming\npm-cache\_npx\18796\node_modules\yarn-audit-fix\target\es5\index.js:105:12)
      at C:\Users\<user>\AppData\Roaming\npm-cache\_npx\18796\node_modules\yarn-audit-fix\target\es5\index.js:179:21
      at step (C:\Users\<user>\AppData\Roaming\npm-cache\_npx\18796\node_modules\yarn-audit-fix\target\es5\index.js:33:23)
      at Object.next (C:\Users\<user>\AppData\Roaming\npm-cache\_npx\18796\node_modules\yarn-audit-fix\target\es5\index.js:14:53)
      at C:\Users\<user>\AppData\Roaming\npm-cache\_npx\18796\node_modules\yarn-audit-fix\target\es5\index.js:8:71
      at new Promise (<anonymous>)
      at __awaiter (C:\Users\<user>\AppData\Roaming\npm-cache\_npx\18796\node_modules\yarn-audit-fix\target\es5\index.js:4:12) {
    errno: -4058,
    code: 'ENOENT',
    syscall: 'spawnSync C:\\Users\\<user>\\AppData\\Roaming\\npm-cache\\_npx\\18796\\node_modules\\yarn-audit-fix\\node_modules\\.bin\\npm',
    path: 'C:\\Users\\<user>\\AppData\\Roaming\\npm-cache\\_npx\\18796\\node_modules\\yarn-audit-fix\\node_modules\\.bin\\npm',
    spawnargs: [
      'audit',
      'fix',
      '--package-lock-only',
      '--prefix=C:\\data\\src\\<project>\\node_modules\\.cache\\yarn-audit-fix'
    ]
  },
  status: null,
  signal: null,
  output: null,
  pid: 0,
  stdout: null,
  stderr: null
}

antongolub · 2020-08-21T11:28:24Z

Again my carelessness. Sorry. I have not posted the latest edits:

exports.getNpm = function () { return path_1.resolve(require.resolve('npm'), '../../../.bin/npm'); };

should be

export const getNpm = () => resolve(require.resolve('npm'), '../../../.bin', isWindows() ? 'npm.cmd' : 'npm')

2.0.0-rc.10 is waiting for review.

klues · 2020-08-21T11:45:01Z

unfortunately still looks the same as rc.9

antongolub · 2020-08-21T11:50:19Z

Looks like I'm having some kind of publishing issue. Try out rc.11 please.

MattSwartz · 2020-08-21T13:00:25Z

rc.11 does get past the first part then bombs out here:


found 0 vulnerabilities
npm timing command:audit Completed in 19147ms
npm verb exit [ 0, true ]
npm timing npm Completed in 19956ms
npm info ok
Updating yarn.lock from package-lock.json...
TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at flattenPackageLock (C:\Users\matt\AppData\Roaming\npm-cache\_npx\44120\node_modules\yarn-audit-fix\node_modules\@antongolub\synp\util\format.js:7:17)
    at buildYarnTree (C:\Users\matt\AppData\Roaming\npm-cache\_npx\44120\node_modules\yarn-audit-fix\node_modules\@antongolub\synp\lib\lockfileV1\tree.js:22:34)
    at convertNpmV1ToYarn (C:\Users\matt\AppData\Roaming\npm-cache\_npx\44120\node_modules\yarn-audit-fix\node_modules\@antongolub\synp\lib\lockfileV1\index.js:26:22)
    at convertNpmV2ToYarn (C:\Users\matt\AppData\Roaming\npm-cache\_npx\44120\node_modules\yarn-audit-fix\node_modules\@antongolub\synp\lib\lockfileV2\index.js:84:12)
    at convertNpmToYarn (C:\Users\matt\AppData\Roaming\npm-cache\_npx\44120\node_modules\yarn-audit-fix\node_modules\@antongolub\synp\lib\index.js:31:9)
    at Object.npmToYarn (C:\Users\matt\AppData\Roaming\npm-cache\_npx\44120\node_modules\yarn-audit-fix\node_modules\@antongolub\synp\index.js:17:12)
    at yarnImport (C:\Users\matt\AppData\Roaming\npm-cache\_npx\44120\node_modules\yarn-audit-fix\target\es5\index.js:114:39)
    at C:\Users\matt\AppData\Roaming\npm-cache\_npx\44120\node_modules\yarn-audit-fix\target\es5\index.js:179:21
    at step (C:\Users\matt\AppData\Roaming\npm-cache\_npx\44120\node_modules\yarn-audit-fix\target\es5\index.js:33:23)

antongolub · 2020-08-21T13:38:01Z

In any case, this is a step forward.

antongolub · 2020-08-21T13:54:20Z

@MattSwartz, could you share a link to your repo? As far as I understand, this issue is related to synp, and invokes code of 2017.

package.json + yarn.lock would be enough

klues · 2020-08-21T14:33:33Z

rc.11 worked for me, thank you very much for your efforts! 👍

MattSwartz · 2020-08-21T20:53:05Z

https://gist.github.com/MattSwartz/710103987633f938a851ba8d80bfe286 let me know if this helps. This is a private repo so I can't share a link to it.

antongolub · 2020-08-22T09:20:55Z

@MattSwartz

I think this is enough for research. Let's deal with this separately: #20

antongolub · 2020-09-01T06:53:08Z

If there is no objections, I'm going to close this for now as the main issue seems to be solved.

antongolub added the bug Something isn't working label Aug 20, 2020

antongolub self-assigned this Aug 20, 2020

antongolub mentioned this issue Aug 21, 2020

Synp fails on attempt to convert undefined or null to object #20

Closed

antongolub closed this as completed Sep 1, 2020

SleeplessByte mentioned this issue May 8, 2021

Regression: EPERM operation not permitted on Windows #120

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Errors running on windows in git bash: EPERM operation not permitted, could not find parent dir #18

Errors running on windows in git bash: EPERM operation not permitted, could not find parent dir #18

klues commented Aug 20, 2020

antongolub commented Aug 20, 2020 •

edited

Loading

MattSwartz commented Aug 20, 2020

antongolub commented Aug 20, 2020 •

edited

Loading

antongolub commented Aug 20, 2020

klues commented Aug 21, 2020

antongolub commented Aug 21, 2020 •

edited

Loading

klues commented Aug 21, 2020

antongolub commented Aug 21, 2020

antongolub commented Aug 21, 2020

klues commented Aug 21, 2020

antongolub commented Aug 21, 2020

klues commented Aug 21, 2020

antongolub commented Aug 21, 2020 •

edited

Loading

MattSwartz commented Aug 21, 2020 •

edited

Loading

antongolub commented Aug 21, 2020

antongolub commented Aug 21, 2020 •

edited

Loading

klues commented Aug 21, 2020

MattSwartz commented Aug 21, 2020

antongolub commented Aug 22, 2020

antongolub commented Sep 1, 2020

Errors running on windows in git bash: EPERM operation not permitted, could not find parent dir #18

Errors running on windows in git bash: EPERM operation not permitted, could not find parent dir #18

Comments

klues commented Aug 20, 2020

antongolub commented Aug 20, 2020 • edited Loading

MattSwartz commented Aug 20, 2020

antongolub commented Aug 20, 2020 • edited Loading

antongolub commented Aug 20, 2020

klues commented Aug 21, 2020

antongolub commented Aug 21, 2020 • edited Loading

klues commented Aug 21, 2020

antongolub commented Aug 21, 2020

antongolub commented Aug 21, 2020

klues commented Aug 21, 2020

antongolub commented Aug 21, 2020

klues commented Aug 21, 2020

antongolub commented Aug 21, 2020 • edited Loading

MattSwartz commented Aug 21, 2020 • edited Loading

antongolub commented Aug 21, 2020

antongolub commented Aug 21, 2020 • edited Loading

klues commented Aug 21, 2020

MattSwartz commented Aug 21, 2020

antongolub commented Aug 22, 2020

antongolub commented Sep 1, 2020

antongolub commented Aug 20, 2020 •

edited

Loading

antongolub commented Aug 20, 2020 •

edited

Loading

antongolub commented Aug 21, 2020 •

edited

Loading

antongolub commented Aug 21, 2020 •

edited

Loading

MattSwartz commented Aug 21, 2020 •

edited

Loading

antongolub commented Aug 21, 2020 •

edited

Loading