Jeroen Claassens

> No idea why but removing the package-lock.json and the /node_modules folder and reinstall solved the issue. That would be because package-lock ***locks*** version installs to whatever it has specified....

@amazingzcj did you ever figure this out? I'm facing the same issue right now. Both on latest versions of this lib, react-router and react-router-dom as well as on v6.0.0 and...

I'm not sure what exactly it was but I managed to.. solve... It? I use this lib v6.4.0, react-router and react-router-dom v5 and v6 of react-redux. Turns out the problem...

@amazingzcj I've posted it on Gist here: https://gist.github.com/Favna/f4e7bf31cd8240d9d0fb9f2501b7e47c See the comment after all the files for a table of contents of sorts.

I just found this issue when looking for solutions to my current code formatting conflict between eslint and prettier and I'd like to know if there's anything to resolve it....

Sadness. So that basically means I cannot use Prettier because there is no option to disable that new line formatting.

@j-f1 It's not an eslint rule that causes the issue. Eslint doesn't care if you put destructured objects across 1 line. The closest thing to it is [object-property-newline](https://eslint.org/docs/rules/object-property-newline) but even...

> The `graphql-parse-resolve-info` upgrade is blocked by [graphql/graphql-js#2719](https://github.com/graphql/graphql-js/issues/2719), but it's not a dependency of type-graphql anyway. I agree it's not a dependency but at least to my knowledge there aren't...

> Federation already supports v16, it's only `graphql-modules` and `graphql-redis-subscriptions` that lack support. Did I miss something...? I thought `graphql-parse-resolve-info` also didn't support v16 yet, but you didn't list it...

Hi there, is there any known priority grade for this issue? Of course, there is no ETA to give, I understand that, but it would be nice to know if...