Error EPERM: operation not permitted, version 1.1.9

[sofyan-ahmad]

When I tried to run 'sls deploy', the following error is shown:

EPERM: operation not permitted, unlink '/Users/sofyan.ahmad/Projects/project-name/.build/node_modules'

The error is gone when I reverted back to version 1.1.7

[JackCuthbert]

I am unable to reproduce this one 😞 Are you using webpack? There's another issue surrounding webpack users at the moment which may be related.

Have you tried removing the .build and .serverless folders?

[up4]

I have the same problem, on macOS as well.

Appending debug log here.

`SLS_DEBUG=* npx sls deploy --stage prod -v
Serverless: Load command config
Serverless: Load command config:credentials
Serverless: Load command create
Serverless: Load command install
Serverless: Load command package
Serverless: Load command deploy
Serverless: Load command deploy:function
Serverless: Load command deploy:list
Serverless: Load command deploy:list:functions
Serverless: Load command invoke
Serverless: Load command invoke:local
Serverless: Load command info
Serverless: Load command logs
Serverless: Load command metrics
Serverless: Load command print
Serverless: Load command remove
Serverless: Load command rollback
Serverless: Load command rollback:function
Serverless: Load command slstats
Serverless: Load command plugin
Serverless: Load command plugin
Serverless: Load command plugin:install
Serverless: Load command plugin
Serverless: Load command plugin:uninstall
Serverless: Load command plugin
Serverless: Load command plugin:list
Serverless: Load command plugin
Serverless: Load command plugin:search
Serverless: Load command config
Serverless: Load command config:credentials
Serverless: Load command rollback
Serverless: Load command rollback:function
Serverless: Load command login
Serverless: Load command logout
Serverless: Load command generate-event
Serverless: Load command test
Serverless: Load command dashboard
Serverless: Invoke deploy
Serverless: Invoke package
Serverless: Invoke aws:common:validate
Serverless: Invoke aws:common:cleanupTempDir
Serverless: Compiling with Typescript...
Serverless: Using local tsconfig.json
Serverless: Typescript compiled.

Error --------------------------------------------------

EPERM: operation not permitted, unlink '/Users/up4/api/.build/node_modules'

 For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

Stack Trace --------------------------------------------

Error: EPERM: operation not permitted, unlink '/Users/up4/api/.build/node_modules'
at Object.unlinkSync (fs.js:976:3)
at TypeScriptPlugin. (/Users/up4/api/node_modules/serverless-plugin-typescript/src/index.ts:195:12)
at Generator.next ()
at /Users/up4/api/node_modules/serverless-plugin-typescript/dist/src/index.js:7:71
at new Promise ()
at __awaiter (/Users/up4/api/node_modules/serverless-plugin-typescript/dist/src/index.js:3:12)
at TypeScriptPlugin.copyDependencies (/Users/up4/api/node_modules/serverless-plugin-typescript/dist/src/index.js:166:16)
at TypeScriptPlugin. (/Users/up4/api/node_modules/serverless-plugin-typescript/src/index.ts:45:20)
at Generator.next ()
at fulfilled (/Users/up4/api/node_modules/serverless-plugin-typescript/dist/src/index.js:4:58)
at processTicksAndRejections (internal/process/task_queues.js:85:5)
From previous event:
at PluginManager.invoke (/Users/up4/api/node_modules/serverless/lib/classes/PluginManager.js:464:22)
at PluginManager.spawn (/Users/up4/api/node_modules/serverless/lib/classes/PluginManager.js:484:17)
at Deploy. (/Users/up4/api/node_modules/serverless/lib/plugins/deploy/deploy.js:115:50)
From previous event:
at Object.before:deploy:deploy [as hook] (/Users/up4/api/node_modules/serverless/lib/plugins/deploy/deploy.js:100:30)
at /Users/up4/api/node_modules/serverless/lib/classes/PluginManager.js:464:55
From previous event:
at PluginManager.invoke (/Users/up4/api/node_modules/serverless/lib/classes/PluginManager.js:464:22)
at PluginManager.run (/Users/up4/api/node_modules/serverless/lib/classes/PluginManager.js:496:17)
at /Users/up4/api/node_modules/serverless/lib/Serverless.js:116:33
at processImmediate (internal/timers.js:439:21)
at process.topLevelDomainCallback (domain.js:126:23)
From previous event:
at Serverless.run (/Users/up4/api/node_modules/serverless/lib/Serverless.js:103:74)
at /Users/up4/api/node_modules/serverless/bin/serverless.js:52:28
at /Users/up4/api/node_modules/graceful-fs/graceful-fs.js:111:16
at /Users/up4/api/node_modules/graceful-fs/graceful-fs.js:45:10
at FSReqCallback.oncomplete (fs.js:153:23)
From previous event:
at /Users/up4/api/node_modules/serverless/bin/serverless.js:52:6
at processImmediate (internal/timers.js:439:21)
at process.topLevelDomainCallback (domain.js:126:23)
From previous event:
at Object. (/Users/up4/api/node_modules/serverless/bin/serverless.js:38:39)
at Module._compile (internal/modules/cjs/loader.js:776:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
at Module.load (internal/modules/cjs/loader.js:643:32)
at Function.Module._load (internal/modules/cjs/loader.js:556:12)
at Function.Module.runMain (internal/modules/cjs/loader.js:839:10)
at /usr/local/lib/node_modules/npm/node_modules/libnpx/index.js:268:14

Get Support --------------------------------------------
Docs: docs.serverless.com
Bugs: github.com/serverless/serverless/issues
Issues: forum.serverless.com

Your Environment Information ---------------------------
Operating System: darwin
Node Version: 12.6.0
Serverless Version: 1.48.3
Enterprise Plugin Version: 1.3.2
Platform SDK Version: 2.1.0`

[up4]

And reverting from 1.1.9 to 1.1.7 worked for me as well.

[ThomasEg]

We are having to problem aswell... no WebPack and on Windows...

[ThomasEg]

I honestly don't think serverless-plugin-typescript is to "blame" for this. I think something in the underlying fs-package messes up symlinks...

I've managed to fix this error by deleting the .build/.serverless/whatever directories and node-modules-directory... that solved the issue for me...

[JackCuthbert]

@ThomasEg I tend to agree, I've had a heap of issues getting symlink code to work across *nix and Windows. Windows doesn't allow symlinks without administrator level permissions (ref) and there are already a heap of flaky workarounds for exactly that problem (likely causing this issue).

Making matters worse is the fact that this plugin tries to support webpack configurations which change the expected output directory/file on top of TypeScript ones (aside: why do people feel they need to use this plugin in addition to webpack + ts-loader or similar?), I'm beginning to think that the scope of this plugin is far too large to be reasonably maintainable for just one person. Perhaps @divyenduz can weigh in here?

[ThomasEg]

@JackCuthbert why do people feel they need to use this plugin in addition to webpack + ts-loader or similar?

I have, multiple times, tried to move away from this plugin to webpack, due to issues like this one... but i cannot get a satisfying result. Either i drown in strange runtime-errors i cannot track down or huuuuuuge compiletime...

[andrewoh531]

Downgrading to v1.1.7 worked whilst v1.1.8 (and v1.1.9) errored.

I noticed that with v1.1.7, running sls package will create symlinks for the .build/node_modules directory.

Using v1.1.8 (or v1.1.9) it's no longer a symlink. Something in the v1.1.8 release broke this.

[grigorecezar]

Same issue here. Downgrading to v1.1.7 worked...

[smprime]

folder permissions issue when building:

$ sudo rm -rf .build/

[dcworldwide]

Downgraded to v1.1.7. What a miserable day for productivity this was.

Ensuring adequate permissions for local user on node-modules, .build, .serverless had not affect for me.

[creduo]

Downgraded to 1.1.7 too, working fine