Simen Bekkhus
Simen Bekkhus
I agree it should be fixed! Sorry about the bot 😅
Deprecating on npm is probably enough as people installing would get a warning. Which might be a bit heavy handed of course 😅
Yeah, that seems reasonable to me
a separate config seems fine, but without `overrides` like you mention
🎉 will you publish a new beta release with this, or as `latest`?
Awesome, thanks!
this is what I see with the current release - the `E` seems more readable in that one? Or am I missing something?
Could this be fixed? Workaround is just to remove peer at `flow-typed install` time, but that seems very unnecessary...
Just remove the peer dependency from package.json before running install `jq 'del(.peerDependencies)' package.json > tmp.json && mv tmp.json package.json` (missing stedolan/jq#105...) If you don't want to leave a modified package.json,...
Hey! 👋 Thanks for the PR and sorry for the radio silence. What do you think about just passing a resolver instead? https://jestjs.io/docs/configuration#resolver-string You can then, based on the module...