Enable Fable support in Nuget package

[landy]

Hello, this change should enable the Aether to be used from Fable applications

[et1975]

Does Fable.Aether package not work for you?

[landy]

I think that it makes sense to have it in the original library.

[njlr]

I would also like to see Fable support in the main package. Since I am sharing code between client and server, this would make it easier to keep everything in sync.

[et1975]

Sharing the code would work just fine, but sharing the project dependencies is something completely different.

[landy]

What do you mean? For example I’m sharing the dependency for https://github.com/demystifyfp/FsToolkit.ErrorHandling and it works just fine.

[njlr]

I am sharing code between client and server. This shared code depends on Aether. Currently I am depending on the file directly from GitHub using Paket's GitHub feature (github xyncro/aether:8.3.1 src/Aether/Aether.fs). However, my understanding is that if I want to use the Nuget packages, I must take two dependencies: Fable.Aether and Aether. The client will depend on Fable.Aether and the server will depend on Aether. I must ensure the versions match up. If the main package (Aether) supported Fable, then I would only need one dependency, making things a bit simpler.

[et1975]

If I'm reading you right you are sharing the code by reusing the project, in which case yes, you have a problem. But imo more typical way to share the code is to include the same sources into different projects. This has been the traditional way of dealing with different target platforms since the days we had to take different dependencies based on x32 and x64.

If you look at elmish for example, there are 2 projects - one for CLR and one for fable. Conditional compilation actually produces different implementations, so even if you could use the same package, it would not have the optimal functionality for both targets.

Not saying Aether package shouldn't include the sources (see #52) but there are alternatives.

[Dzoukr]

Please, is there any update on this? I would appreciate this PR to be merged as well. There is no harm to do so - old code will work and this library could be also used from Fable without any "wrapper" like Fable.Aether.