Jeffrey Wear
Jeffrey Wear
Hm can you determine why? That seems like a bug, which I'd rather not mask with a timeout.
Oh neat find @ccnokes! I'd take a PR for that.
How did you reproduce this? Can't tell from the trace
What's your OS and Node version?
> I've seen a lot of comments around these problems with people saying they've moved to docker instead of messing about with ebextensions so that's what I've done too. Oh...
Hm, it looks like the Elastic Beanstalk staging directory (`/tmp/deployment/application/`) is unclean for some reason. What version of [the EB Node.js platform](http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/concepts.platforms.html#concepts.platforms.nodejs) do you use and what are the contents...
Ok, my next move to debug this would be to check if, when you get the "`/tmp/deployment/application/node_modules` exists" error, `/tmp/deployment/application/node_modules` is a regular folder or already somehow is the symlink...
I think this is an issue in `install-files`, filed https://github.com/mixmaxhq/install-files/issues/14.
Hey @OmgImAlexis, sorry for the late response. If https://github.com/mixmaxhq/cors-gate/blob/a6bce954ddf66420a645029cf2b8c72e9c90a223/index.js#L87-L92 is `false`, we'll be a little less secure since we won't be able to patch the origin in to try to...
Hi @Sly777, you're asking about passing the `max_old_space_size` Node flag through to npm right? That sounds like it might be a good idea but I'm not sure how to do...