Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error: spawn E2BIG

See original GitHub issue

I tried to delete all my node_modules folders, but it seems like I hit some limit. Would it be possible to fix this by letting the trash-cli split up the expanded glob before performing the work?

❯ trash ‘**/node_modules’ Error: spawn E2BIG at exports._errnoException (util.js:1012:11) at ChildProcess.spawn (internal/child_process.js:302:11) at exports.spawn (child_process.js:372:9) at exports.execFile (child_process.js:139:15) at /usr/local/lib/node_modules/trash-cli/node_modules/pify/index.js:29:7 at /usr/local/lib/node_modules/trash-cli/node_modules/pify/index.js:12:10 at ret (/usr/local/lib/node_modules/trash-cli/node_modules/pify/index.js:56:34) at module.exports (/usr/local/lib/node_modules/trash-cli/node_modules/trash/lib/osx.js:37:32) at module.exports (/usr/local/lib/node_modules/trash-cli/node_modules/trash/index.js:22:45) at Object.<anonymous> (/usr/local/lib/node_modules/trash-cli/cli.js:27:1) ~/Devel 1m 49s

Issue Analytics

State:
Created 7 years ago
Reactions:3
Comments:7 (4 by maintainers)

Top GitHub Comments

2reactions

sindresorhuscommented, Jan 28, 2017

@BenGitsCode Yeah. I usually use del-cli for deleting node_modules as it’s not something I would ever care about recovering.

1reaction

sindresorhuscommented, Jan 28, 2017

@dawsonbotsford No, that’s not what I’m saying. That would be very surprising behavior. I just use del-cli instead of trash when deleting node_modules.