Unable to specify project dependencies when using autolinking/npm package

[dunhor]

The scenario is basically this:

---

Some React Native Windows application 'A' has, as a part of it, a custom-written WinRT component 'C'. 'A' wishes to consume 'C' via JavaScript and would like to use React Native WinRT to do so.

---

As it stands today, this is not possible (AFAIK) when using autolinking/the npm package. The key underlying issue is the inability to specify a ProjectReference in the WinRTTurboModule project's vcxproj because the project file is a part of the npm package. We might be able to work around this using properties in the ExperimentalFeatures.props file, however I'm unsure how we might go about this, and it would undoubtedly be a hacky workaround.

Another option might be to address this in React Native Windows itself by adding the ability to specify such dependencies somehow. But again, I'm not really sure what that would look like. Perhaps all autolinked modules could have dependencies on all non-app projects, but I'm not sure what that might break.

The last option would be to do nothing. Anyone with a custom WinRT component is likely already a "power user" so following the steps for consuming the nuget package and manually creating a project wouldn't be that foreign to them.