Skip to content

increase exec max buffer#6236

Merged
deepu105 merged 1 commit intojhipster:masterfrom
ruddell:increase-exec-max-buffer
Aug 16, 2017
Merged

increase exec max buffer#6236
deepu105 merged 1 commit intojhipster:masterfrom
ruddell:increase-exec-max-buffer

Conversation

@ruddell
Copy link
Copy Markdown
Member

@ruddell ruddell commented Aug 15, 2017

As a user's project grows, the build process can fail due to the same issue as in #6059, a specific example is @dancancro's Great Big Example Application. The only way for a developer to work around this is to modify generator-jhipster code.

I took the default value from execa which uses 10MB. NodeJS was going to use 1024*1024 but the PR was closed for inactivity (nodejs/node#11196) and this doesn't seem to be enough (see @dancancro's comment here).

@ruddell ruddell force-pushed the increase-exec-max-buffer branch from a9019d7 to dee92a2 Compare August 15, 2017 23:31
@deepu105 deepu105 merged commit 6e19f35 into jhipster:master Aug 16, 2017
@ruddell ruddell deleted the increase-exec-max-buffer branch August 16, 2017 21:58
@jdubois jdubois modified the milestone: 4.7.0 Aug 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants