Closed stevekuznetsov closed 7 months ago
Fixes #342
The package "expo-modules-autolinking" should not be installed directly in your project. It is a dependency of other Expo packages, which will install it automatically as needed.
The package "@types/react-native" should not be installed directly in your project, as types are included with the "react-native" package.
One or more checks failed, indicating possible issues with the project.
lol. OK, whatever
You may need to nuke the current modules and do a clean install:
rm -fr node_modules
yarn install --frozen-lockfile
I'll double check console messages with what I've got.
Thanks, ran that locally. The jest
errors reproduced in CI - maybe we also need to cache-bust the module cache in actions?
A changing yarn.lock
should invalidate the cache https://github.com/actions/setup-node#caching-global-packages-data
Hm - well, if you don't see any downsides to having the extra mocks and ts-node
in the dev dependencies, maybe nothing to do here?
The GraphQL schemas we were working with are not useful anyway.