Hi Victoria
Thanks for investigating - that seems to fix the problem. I've committed
the fix.
Regards, Dave.
On Thu, May 31, 2018 at 10:32 AM, Victoria Henry wrote:
> Hey Dave,
>
> The reason that it was taking so long was because the linter was acting on
> the javascript in the ycache
Hey Dave,
The reason that it was taking so long was because the linter was acting on
the javascript in the ycache directory in the container. The fix is to add
the ycache directory to the .eslintignore file. We can send a patch file,
if you’d like:
diff --git a/web/.eslintignore
Hi
So it turns out the hang was a result of:
=
Using the '.eslintignore' config file for excluding the temporary,
vendor specific, and templates files, instead of writing our own logic
to do so.
Patch by: Anthony & Joao
Reviewed by: Khushboo
Branch
--
master
Details
---
Hi
The container build is hanging for me on 2 different machines at:
20:19:50 $ cross-env NODE_ENV=production yarn run bundle:dev
20:19:51 $ yarn run linter && yarn run webpacker
20:19:52 $ yarn eslint --no-eslintrc -c .eslintrc.js --ext .js --ext .jsx .
20:19:52 $
