useRouter, useLinkProps, and handleLinkClick missing from react-aria monopackage

[alex2]

Provide a general summary of the issue here

While switching over to the monopackages we've been able to use monopackages for everything except handleLinkClick, useLinkProps, and useRouter from @react-aria/utils, please could you add those to the exports barrel file?

The particular issue with these not being in the monopackage is that we've had issues where downstream users of our component library have had their react-aria and @react-aria/utils diverge causing the react link context definition and consumption to act on two different contexts, resulting in really horrible, hard-to-diagnose bugs in link handling.

The router and link functionality is so foundational in the react-aria world that I think it's important that users be able to decompose useLink and access the router context to more deeply integrate their low-level components. This is currently possible using the sub-package implying it's not a private API, but not in the monopackage.

🤔 Expected Behavior?

Monopackages would help to avoid version mismatches that can drive dual package hazard context bugs.

😯 Current Behavior

We're seeing downstream dual package hazard bugs.

💁 Possible Solution

No response

🔦 Context

No response

🖥️ Steps to Reproduce

N/A

Version

I'm not using react-spectrum; RAC 1.17.0

What browsers are you seeing the problem on?

Chrome

If other, please specify.

No response

What operating system are you using?

N/A

🧢 Your Company/Team

No response

🕷 Tracking Issue

No response

[devongovett]

These are not public APIs. What are you using them for? For now they can be imported from react-aria/private/utils/openLink, or continue to use @react-aria/utils which re-exports from there. In general, if an API is not documented, then it's probably not intended for public consumption.