dominicfraser

Using: ``` "lint": "eslint --ignore-path .gitignore .", ``` also works. https://eslint.org/docs/user-guide/configuring/ignoring-code#using-an-alternate-file This comment seems correct, and this is one example of working around it for now: https://github.com/facebook/create-react-app/issues/8936#issuecomment-674060591

@pladaria, would this fix your issue? https://github.com/benmosher/eslint-plugin-import/pull/1494

Hey Pascal 🙂 For what you are describing it sounds [Differencify](https://github.com/NimaSoroush/differencify) might be a suitable tool, it allows easy taking and comparison of visual snapshots. There are some examples in...

Hey @pokebadgerswithspoon - your build was failing for the same reason as mine, some code formatting in equal.js that grunt had no problem with but the cli did. I updated...

Hey @brutalcrozt - your build was failing for the same reason as mine, some code formatting in equal.js that grunt had no problem with but the cli did. I updated...

It was pure chance unfortunately, searching around issues and finding someone who mentioned using `.Fail` -> I tried it on that rule and it also worked!

@bschlenk We'd also love to be able to allow any component prop based on a prefix, for very similar reasons. Keeping an interested eye on the discussion here.

Now that our projects have moved to React 17 we are now also seeing this warning from another npm package we use that itself uses `recompose`. Our assumption is that...