Windows fails with EPERM: operation not permitted, all files are read-only

[oscar-b]

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
When performing any operation with yarn (add for instance) it errors with:

EPERM: operation not permitted, open 'C:\foo\node_modules\firebase\app-node.js'
at Error (native)

If the current behavior is a bug, please provide the steps to reproduce.

1. Use Windows :(
2. Use yarn
3. Failure

To fix the issue, right click the node_modules folder and un-check "Read-only". Wait. Re-run yarn command. Now it works, like magic! After yarn is done, all files are back to being read-only though.

What is the expected behavior?
Shouldn't have to mark the files as readable.

Please mention your node.js, yarn and operating system version.
node v6.3.1
yarn v0.15.1
Windows 10 (anniversary edition)

[Daniel15]

To fix the issue, right click the node_modules folder and un-check "Read-only".

Is Yarn marking node_modules as readonly, or is something else doing that? I can't repro on Windows with a brand new app (ie. yarn init && yarn add react)

[oscar-b]

Hi @Daniel15

Could you please try this in a clean directory?

yarn init
yarn add firebase
yarn add react

The last command gives me:

C:\Dev\yarntest>yarn add react
yarn add v0.15.1
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
error EPERM: operation not permitted, open 'C:\Dev\yarntest\node_modules\firebase\app-node.js'
    at Error (native)
info Visit http://yarnpkg.com/en/docs/cli/add for documentation about this command.

I'm not sure if it's something the firebase packages does?

[oscar-b]

For clarification; I tried the same steps but with react and eslint and didn't see the same error.

[Daniel15]

Thanks for the information! I can replicate the issue on Windows but not on Debian Linux.

[danielkcz]

I would say this is more of a critical error as it prevents even basic use of Yarn in any project using firebase module.

Removing read-only flag recursively works, but only temporarily. Even running just yarn reruns whole linking dependencies phase and returns these read-only flags back.

Creating fresh project with yarn init and installing any single dependency sets read-only flag to all directories (not files) starting from node_modules. However in case of firebase module, the files are also read-only for some reason. Doing same thing with NPM does not set read-only to files.

[wclr]

Yes this is quite annoying.

@Daniel15
Another problem I have I install the package and on postinstall step it sets chmod some-file 400, and while some operations yarn fail with a like error on this file, (if I set permissions to 644 it runs ok). So I hope you fix original issue and my issue will gone too.

[danielkcz]

@Tapppi (quote from issue)

P.S. Regarding #992, you could probably write a oneliner "postinstall" script to fix the permissions after every install.

That would kinda erase usefulness of Yarn, don't you think? Removing those read-only flags makes Yarn do whole linking process again. Only performance save would about using cache instead of downloading over the network every time.