MSBuild scanning makes it difficult to develop and test a module's example

[jaimecbernardo]

For native modules, a common repo structure is having the module's example in the repo's ./example/ path, installing the module in the example through yarn add ...

When developing and testing the application at the same time, this causes a second version of react-native-windows to be copied from ./node_modules/react-native-windows to ./example/node_modules/{module_name}/node_modules/react-native-windows, which conflicts with ./example/node_modules/react-native-windows when building the example.

The current workaround is to delete ./example/node_modules/{module_name}/node_modules/ manually when yarn gets it, but it's hard to understand where the error is coming from at first.

It'd be good if it was possible to avoid it.

[asklar]

This is a consequence of not using a yarn workspace (which would allow sharing dependencies between the module package and the example app package). This may be something worth adding to a "best practices" doc. @rectified95 fyi.