An unhandled promise rejection usually signifies an exception in an async method, or a failure to handle an error. In Node <15, it results in a printed warning, often leading to termination without a non-zero exit code. This means scripts may fail in CI without creating signal by failing the task.

Default node settings can be set via the NODE_OPTIONS environment variable. E.g. `NODE_OPTIONS=-

What would you like to be added:

Adding a binding to a BindingBase property from the XAML should unwrap the binding expression.

For which Platform:

• iOS
• Android
• WebAssembly
• WebAssembly renderers for Xamarin.Forms
• Windows
• Build tasks
• Solution Templates

Anything else we need to know?

This check should also validate for `Binding

Describe the bug
Adding a reference to a ClassLibrary project from a UWP application project generates a XAML compiler warning.

Steps to reproduce the bug

1. Open Visual Studio 2019 (or 2017)
2. Create a new Universal Windows Class Library project
3. Create a new Universal Windows Application project in the same solution
4. Add a reference to the Class Library project from the Appl