Error: EISDIR: illegal operation on a directory, read

[Jason Walker]

I repeatedly receive this error when deploying my hosting project: Error: EISDIR: illegal operation on a directory, read 

Anyone have guidance to offer on how to address the error?  

I should note that this folder is on the google file stream 'G drive' of my computer.  

Below is screenshot of error and contents of the .log file, redacted a bit.

Heres the contents of firebase-debug.log:

[debug] [2019-01-22T17:30:46.339Z] ----------------------------------------------------------------------

[debug] [2019-01-22T17:30:46.342Z] Command:       C:\Program Files\nodejs\node.exe C:\Users\jason\AppData\Roaming\npm\node_modules\firebase-tools\lib\bin\firebase.js deploy

[debug] [2019-01-22T17:30:46.342Z] CLI Version:   6.3.0

[debug] [2019-01-22T17:30:46.342Z] Platform:      win32

[debug] [2019-01-22T17:30:46.342Z] Node Version:  v8.12.0

[debug] [2019-01-22T17:30:46.343Z] Time:          Tue Jan 22 2019 12:30:46 GMT-0500 (Eastern Standard Time)

[debug] [2019-01-22T17:30:46.343Z] ----------------------------------------------------------------------

[debug] 

[debug] [2019-01-22T17:30:46.368Z] > command requires scopes: ["email","openid","https://www.googleapis.com/auth/cloudplatformprojects.readonly","https://www.googleapis.com/auth/firebase","https://www.googleapis.com/auth/cloud-platform"]

[debug] [2019-01-22T17:30:46.368Z] > authorizing via signed-in user

[debug] [2019-01-22T17:30:46.369Z] [iam] checking project ---online for permissions ["firebase.projects.get","firebasehosting.sites.update"]

[debug] [2019-01-22T17:30:46.371Z] >>> HTTP REQUEST POST https://cloudresourcemanager.googleapis.com/v1/projects/---online:testIamPermissions  

[debug] [2019-01-22T17:30:46.602Z] <<< HTTP RESPONSE 200

[debug] [2019-01-22T17:30:46.608Z] >>> HTTP REQUEST GET https://firebase.googleapis.com/v1beta1/projects/---online  

 

[debug] [2019-01-22T17:30:47.277Z] <<< HTTP RESPONSE 200

[info] 

[info] === Deploying to '---online'...

[info] 

[info] i  deploying hosting

[debug] [2019-01-22T17:30:47.288Z] >>> HTTP REQUEST POST https://firebasehosting.googleapis.com/v1beta1/sites/---online/versions  

[debug] [2019-01-22T17:30:48.376Z] <<< HTTP RESPONSE 200

[info] i  hosting[---online]: beginning deploy...

[info] i  hosting[---online]: found 1587 files in public

[debug] [2019-01-22T17:30:50.161Z] [hosting] hash cache [cHVibGlj] not populated

[debug] [2019-01-22T17:30:50.359Z] Error: EISDIR: illegal operation on a directory, read

[error] 

[error] Error: An unexpected error has occurred.

[Michael Bleigh]

Can you try deleting the .firebase directory in your project folder? If you point your public folder at something simpler (e.g. a folder with one text file in it) does it work?

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/c143b536-ee23-4ac7-b115-5fa135dec6c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jason Walker]

I deleted the .firebase folder, did firebase deploy, but got a different error.... screenshot:

[Jason Walker]

If I take the folder and copy it to my C Drive (literally to the windows desktop, and run firebase deploy, then it works!

I noticed that upon copying the folder, I get errors with some google drawing files (.draw), they cant 'copy' over so I have to skip them in the copy process.  Perhaps its related to those files?  Or otherwsie related to the fact this folder is on the 'G: drive' created by google file stream?

On Tuesday, January 22, 2019 at 2:07:04 PM UTC-5, Michael Bleigh wrote:

[Jason Walker]

I think I've isolated the problem. The .gdraw files present in the public directory seem to be directly related with the error. I moved those particular files outside of the public folder and was able to deploy as expected.

[Mackonen J]

Try locating and removing the .npmrc folder that is located in c:/users/your username/.npmrc