Permissions issue with meteor build in 2.1?

Both on our Linux environment and now suddenly on our Windows environment, we are getting this error when doing an ‘npm install’ in our bundle directory:

npm ERR! syscall open
npm ERR! path c:\ausbundle\bundle\programs\server\package.json
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, open 'c:\ausbundle\bundle\programs\server\package.json'
npm ERR!  [Error: EPERM: operation not permitted, open 'c:\ausbundle\bundle\programs\server\package.json'] {
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'open',
npm ERR!   path: 'c:\\ausbundle\\bundle\\programs\\server\\package.json'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.

We build the bundle with the following command: meteor build --directory C:\ausbundle\

This appears to have only happened since going to Meteor 2.1 and seems to be able to be rectified by giving full permissions to the bundle folder and then running the build process again. Unfortunately having to do that every time is not really a lot of fun. Is there an issue that has been introduced with the permissions?

EDIT: Giving the bundle folder full permissions doesn’t resolve the issue on Windows. Our environment is dead in the water :frowning:

Removing the Read Only status on the bundle folder has allowed me to do an npm install… not sure why this is suddenly happening, on two different OS’es. Maybe someone has checked in a read only file?

1 Like

Just a followup on this, haven’t been able to find any suspicious read-only checkins that could have caused this. It’s a mystery and given it’s dead it in this thread, I guess we’re the only people getting the issue… eh. I’ve added an extra step in our deployment to remove the Read Only status from the bundle folder on both Windows and Linux environments. :frowning: