-
Notifications
You must be signed in to change notification settings - Fork 46.9k
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
feat: add recommended config eslint rule #14762
Conversation
LogError: { FetchError: invalid json response body at http://react.zpao.com/builds/master/_commits/d827445a500e497712a1a404c7ccc25779b1df5c/results.json reason: Unexpected token < in JSON at position 0
at /home/circleci/project/node_modules/node-fetch/lib/body.js:48:31
at process._tickCallback (internal/process/next_tick.js:68:7)
name: 'FetchError',
message:
'invalid json response body at http://react.zpao.com/builds/master/_commits/d827445a500e497712a1a404c7ccc25779b1df5c/results.json reason: Unexpected token < in JSON at position 0',
type: 'invalid-json' }
Generated by 🚫 dangerJS |
Thank you for opening a PR for this! I'm presuming the CI failure is an infra issue and unrelated to this change? If so, could someone retrigger CI? :-) |
Rebased this and added the second rule |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution. |
Thanks! |
Tested by copying in the built package in a project and following the added instructions in the readme