Node: Node 8.9.3 File Lock Issue

[sasproul]

Recently upgraded from Node 6.9.4 to node 8.9.3 in Windows 7 in order to get around a TypeError: Object.values is not a function when trying to insert Vuetify 1.0.17 into Vue 2.5.16.

have googled around to correct the error below but i cant turn off my companies anti virus software and i am running on a virtual machine so I cant affect node directly to perform some of the suggested commands, and I don't have admin permission to perform some of the other commands.

dead in the water.

Do you happen to know how to correct this on windows?

The process to upgrade Node will take about 6 weeks because 'it's a process' to get open source approved. If we push to get another version of node approved, is there one that we can be sure wont have this issue?

Thanks

ISSUE
upon gradle build received the error:

npm ERR! path W:DP FW Temdisplay-frameworkgpf-display-frameworkbuildnpmpackagenode_modulesrequirejsbinr.js.4291109701
npm ERR! code EBUSY
npm ERR! errno -4082
npm ERR! syscall rename
npm ERR! EBUSY: resource busy or locked, rename 'W:DP FW Temdisplay-frameworkgpf-display-frameworkbuildnpmpackagenode_modulesrequirejsbinr.js.4291109701' -> 'W:DP FW Temdisplay-frameworkgpf-display-frameworkbuildnpmpackagenode_modulesrequir.js'

npm ERR! A complete log of this run can be found in:
npm ERR! C:UsersaqureshAppDataRoamingnpm-cache_logs2018-09-27T19_01_47_499Z-debug.log
FAILED

Process 'command 'npm.cmd'' finished with non-zero exit value -4082

[sagitsofan]

Doesn't looks like a node issue, but a frameworks error.

Maybe if you exclude this file in your anti virus rules.

[BridgeAR]

Please ask help questions in the help repository.

But as @sagitsofan already mentioned, it does not seem to be an issue with Node.js.

[sasproul]

exclude what file? If you are suggesting that I disable antivirus on r.js, the error will simply move on to lock up another file in my dependency list. I've seen this occur on multiple files, randomly, in my dependency list.

I am unclear what you mean by " it looks like a frameworks error" but I can tell you that the exact same application builds just fine with Node 6.9.4. This issue was introduced with the update to Node 8.9.3

I'm also seeing that this version of node and npm have caused these same types of issues for other people.
https://github.com/npm/npm/issues/13461
https://github.com/MitocGroup/deep-framework/issues/273
https://github.com/opencollective/opencollective-cli/issues/8
https://stackoverflow.com/questions/36566236/npm-install-error-code-ebusy-errono-4082

To recap - I cant touch my antivirus, I cant run as administrator, I cant run commands as administrator.

To upgrade Node takes 4-6 week while I get approval. If you are telling me that there is no solution I can apply to this anomaly, what version of node.js that is compatible with Windows 7 that does not cause this issue?

On Fri, Sep 28, 2018, 12:15 AM Sagi Tsofan [e-mail] wrote:

Doesn't looks like a node issue, but a frameworks error.

Maybe if you exclude this file in your anti virus rules.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nodejs/node/issues/23135#issuecomment-425323220, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Apl99S5J39z8-9LtV2BIqx6zDf9kUaIvks5ufbCHgaJpZM4W9grM
.