You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To put it simply: React Native makes assumptions that rely on the existence of the node_modules folder.
Since there is no node_modules in PnP, these references need to be updated.
In late 2018, a Github issue was opened on react-native-community/cli to track progress on PnP support. However — almost four years later — there’s not been much progress.
Former Meta engineer Christoph Nakazawatweeted earlier this year that a switch Yarn Berry had been attempted internally, but was abandoned due to technical issues. It seems like PnP support is not a priority at Meta, so the best we can do for now is work around it.
아래의 article을 참고하면 공식적인 RN의 지원 없이 yarn berry가 가지는 이점을 가져갈 수 있어 보이지만 적용시 프로젝트 진행중에 다른 오류가 발생할 수 있을 거 같아 일단 적용하지 않았습니다.
Issues
1. Yarn Classic
React-Native 환경에서 yarn berry2가 정식으로 지원되지 않아 ( 더욱 명확히는 pnp를 지원하지 않음) 대신 yarn classic을 적용해놓았습니다.
Related Issue: react-native-community/cli#27
아래의 article을 참고하면 공식적인 RN의 지원 없이 yarn berry가 가지는 이점을 가져갈 수 있어 보이지만 적용시 프로젝트 진행중에 다른 오류가 발생할 수 있을 거 같아 일단 적용하지 않았습니다.
reference: How to use Yarn 3 with React Native
2. Project Setting
기존 client project와 동일하게 prettier, eslint등 기본 설정이 필요해보입니다.
@doyoonear @hwangyena
The text was updated successfully, but these errors were encountered: