Allow avoiding nuget dependency on ChilliCream.Nitro.App

[janthomasQS]

Product

Hot Chocolate

Is your feature request related to a problem?

Currently referencing HotChocolate.AspNetCore always pulls in the package ChilliCream.Nitro.App.

If one does not need the Nitro-Frontend in ones application then this is undesirable because it pulls in further dependencies like Yarp.ReverseProxy and copies a large 17MB assembly to the output.
Additionally ChilliCream.Nitro.App does not have a well known open-source license. If a HotChocolate user has a license approval process to check that all referenced libraries follow a license whitelist then ChilliCream.Nitro.App needs special handling because of its license.

The solution you'd like

It would be nice if Nitro would be a seperate package that HotChocolate.AspNetCore does not depend on.
This way users who do not need Nitro would avoid the huge dll and the potential licensing pains with it.
If one wants Nitro they could reference this nuget package for nitro and enable it with an extension function.
This can of course be done by default in the project templates.

[michaelstaib]

We will not unbundle Nitro from HotChocolate. But we hear you on the license issue and package size. What we will do for version 17 is to split Nitro into two parts, one part the core part will become part of HotChocolate pipeline packages. This means for most people everything will be as before. However the embedded resources will become separate and will not be referenced. This means that everything will be MIT and there is no large resources bundled.