Added my own fork of react-native-copilot so that Expo CLI does not keep warning me about it

[Proman4713]

📝 Why & how

Add a new library

✅ Checklist

• Added library to react-native-libraries.json
• Updated library in react-native-libraries.json

[Simek]

Hey @Proman4713, can you share the screenshot of warning you are wanting to resolve?

[Proman4713]

@Simek i'll also test the other libs and see if they work, then I will add them to the directory if they show no issues!

[Simek]

Thanks for sharing! What's the exact command you are executing? Since we do the validation in CLI, in two places, and one more check is also made by expo-doctor.

[Simek]

We offer a way to customize the checks and ignore given packages or scopes (usually local one, or private forks), but it might not apply in all cases when the check is performed, hence the question before recommending that approach:

• https://docs.expo.dev/versions/latest/config/package-json/#reactnativedirectorycheck

[Proman4713]

expo doctor

[Proman4713]

i dont want to exclude these libraries from the directory check, why can't I just properly tell the directory whether or not they work for the new architecture?

[Simek]

Usually it's easier to ignore private forks and packages than listing all of the forks of existing libraries. If we would do that, then the directory would be in tens of thousands entries, and the usability of it would be questionable due to shear amount of data, so we need to have some limiting factor.

You initial PR comment suggested directly that your package is not created to be used by others, it's just a fork for your own purpose, and repo stats reflect that. That's why I have suggested excluding the check. If your fork grow, and got some other users usage and traction, there is no reason why it cannot be added later in time.

[Proman4713]

Alright, you have got a point.. I will manually exclude the fork on my end... But I'll still test the other packages and make PRs for them if they work