Could someone explain requirements a bit more?

[Jonathan Jacobs (jonathanj)]

The requirements documentation mentions that "microsoft/react-native/0.70 will be used for development", in the context of the example earlier in the docs. But it's not clear what microsoft/react-native/0.70 is in this case.

Does it refer to this profile declared in the presets?

What am trying to do is use align-deps for a non-RN (utility) package in a monorepo containing RN apps, but I can't omit requirements so I'm trying to understand how to correctly define it when the package does not (and should not) depend on RN itself.

Would greatly appreciate any advice!

[Tommy Nguyen (tido64)]

Hi Jonathan Jacobs (@jonathanj).

Does it refer to this profile declared in the presets?

Yes, that's correct. Specifically, this profile: packages/align-deps/src/presets/microsoft/react-native/profile-0.70.ts

What am trying to do is use align-deps for a non-RN (utility) package in a monorepo containing RN apps, but I can't omit requirements so I'm trying to understand how to correctly define it when the package does not (and should not) depend on RN itself.

In the requirements section, you specify that your package needs. Instead of react-native@0.70, you could state react@17 if your package requires React 17.x.

I hope that makes sense.

[Jonathan Jacobs (jonathanj)]

Thanks for the reply Tommy Nguyen (@tido64), that does help clear it up, thanks.

I have a follow-up question then, out of curiosity: requirements as an arbitrary package name that my package needs (like in the most fundamental sense) seems sort of arbitrary to me. From my (a user's) point of view, this could also be achieved as a capability? So I assume that requirements is useful to align-deps in some other way, I'm just not sure what that way is, would you mind explaining it or pointing me to the documentation I may have missed on the subject?

[Tommy Nguyen (tido64)]

The design document we wrote contains a lot more details: https://microsoft.github.io/rnx-kit/docs/architecture/dependency-management

It still uses the old terminologies from 1.x, but I still think you should be able to grasp some of the basic concepts. Let me know if things are still unclear after reading it. We can always improve our docs.

[Jonathan Jacobs (jonathanj)]

Thanks, that makes it clearer to me. I appreciate the feedback!