Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: spawn E2BIG #40

Closed
yoshuawuyts opened this issue Feb 21, 2015 · 4 comments

Comments

@yoshuawuyts
Copy link
Contributor

commented Feb 21, 2015

Using standard@2.7.0 and io.js@1.3.0:

~/src/yw/finfin master*  7s
❯ npm t

> finfin@1.0.0 test /Users/yoshuawuyts/src/yw/finfin
> standard && NODE_ENV=test node test | colortape

child_process.js:1132
    throw errnoException(err, 'spawn');
          ^
Error: spawn E2BIG
    at exports._errnoException (util.js:734:11)
    at ChildProcess.spawn (child_process.js:1132:11)
    at Object.exports.spawn (child_process.js:964:9)
    at spawn (/Users/yoshuawuyts/src/yw/finfin/node_modules/standard/index.js:
162:20)
    at /Users/yoshuawuyts/src/yw/finfin/node_modules/standard/node_modules/run
-parallel/index.js:32:7
    at Array.forEach (native)
    at module.exports (/Users/yoshuawuyts/src/yw/finfin/node_modules/standard/
node_modules/run-parallel/index.js:31:11)
    at /Users/yoshuawuyts/src/yw/finfin/node_modules/standard/index.js:136:7
    at done (/Users/yoshuawuyts/src/yw/finfin/node_modules/standard/node_modul
es/run-parallel/index.js:15:13)
    at /Users/yoshuawuyts/src/yw/finfin/node_modules/standard/index.js:157:7
npm ERR! Test failed.  See above for more details.

~/src/yw/finfin master*

Google doesn't seem to be familiar with these popping up in node. Maybe anyone's had this happen before? The project can be found here in case you want to replicate. Thanks!

@feross

This comment has been minimized.

Copy link
Member

commented Feb 21, 2015

E2BIG means that the argument list is too long. See errors.c where it's defined.

I cloned your project and it worked fine for me, on iojs 1.3.0, so this must be an operating system difference. What OS are you using?

Please run getconf ARG_MAX to check the max argument size (in bytes) of your OS.

Also, please install the latest version of standard (2.7.1). Verify by running standard --version. Then run DEBUG=standard npm t and paste the output. It should show us the exact command that standard is trying to run under-the-hood (and we can see if there's actually a huge argument list being passed, or not).

@yoshuawuyts

This comment has been minimized.

Copy link
Contributor Author

commented Feb 22, 2015

Hah, I ran standard with DEBUG=standard and it appeared node_modules weren't being ignored in non-root directories. Adding a standard.ignore property to package.json solved it for me. I believe there was a discussion about ignoring node_modules in an issue, but I can't seem to find it (would be useful to link to, I think.) Anyway I'm all good now; thanks! 🎉

@feross

This comment has been minimized.

Copy link
Member

commented Feb 22, 2015

Thanks for sharing the outcome. This settles it. I'll merge the issue to ignore all node_modules folders.

@gdad-s-river

This comment has been minimized.

Copy link

commented Jun 14, 2016

Hey @yoshuawuyts @feross, maybe this isn't the right place to ask this since it's not related to this repo at all, but I'd appreciate if you could help out about this question that I asked on stack overflow. I'm not able to debug the E2BIG error source in my project's grunt build process. If you could help (if that's possible, that is), I really need some help. Thanks

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
3 participants
You can’t perform that action at this time.