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

EMFILE error #1003

Open
kennyx46 opened this Issue Nov 19, 2014 · 3 comments

Comments

Projects
None yet
3 participants
@kennyx46

kennyx46 commented Nov 19, 2014

Hi!
We get an EMFILE error while building project. Probably because of multiple openings of package.json file.
It would be great if we could use custom resolve function for browserify instead of function in browser-resolve. Any other ideas?

@mattdesl

This comment has been minimized.

Show comment
Hide comment
@mattdesl

mattdesl Nov 20, 2014

Contributor

Getting something similar with a project that has a lot of modules. Still trying to find root cause.

EDIT: Was an issue with watchify; updating to latest 2.1.1 fixed it.

Contributor

mattdesl commented Nov 20, 2014

Getting something similar with a project that has a lot of modules. Still trying to find root cause.

EDIT: Was an issue with watchify; updating to latest 2.1.1 fixed it.

@mattdesl

This comment has been minimized.

Show comment
Hide comment
@mattdesl

mattdesl Nov 20, 2014

Contributor

Scratch my last. I'm getting this error on a repo with a lot of modules just running browserify directly on the entry point. It only comes up when I require() another module that also has a lot of modules.

Related: #431

Contributor

mattdesl commented Nov 20, 2014

Scratch my last. I'm getting this error on a repo with a lot of modules just running browserify directly on the entry point. It only comes up when I require() another module that also has a lot of modules.

Related: #431

@startswithaj

This comment has been minimized.

Show comment
Hide comment
@startswithaj

startswithaj Dec 8, 2014

I get this on OSX. Try run ulimit -n 2048 in bash

startswithaj commented Dec 8, 2014

I get this on OSX. Try run ulimit -n 2048 in bash

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment