Слава Україні! Героям слава!

@alfonsogarciacaro Looks like it has `Fable.Core.JsInterop.jsOptions`, but not `Fable.Core.jsOptions`

@MangelMaxime Technically you can stack failure upon failure too, I do it all the time.

@MangelMaxime > We should either includes the other fable-library Yes, we should be including all fable libraries, and the Fable JS CLI should be copying them locally to output folder...

@dbrattli You can convert this to draft PR so it won't be merged until ready.

@dbrattli Just to clarify, while this is a great idea, do you have any concerns about losing some of the (potential) benefits of easy interoperability with other Python code by...

@dbrattli I wonder if it is an option to compile the `fable-library-py` on the fly the first time it compiles a project, to match the target architecture. This would require...

@dbrattli That makes sense, thank you for explaining.

@MangelMaxime I agree, it could be either F# compiler (FCS) doing the optimization, or Fable. If it's in FCS, there may be little we could do, except run in DEBUG...

@lukaszkrzywizna Until we have such an attribute, another workaround that prevents identifiers from being beta-reduced is to mark them as mutable. I know, not very functional, and not very pretty,...

@MangelMaxime I would suggest doing separate PRs, for supporting nullable value type (i.e. `System.Nullable`) and a different PR for nullable ref types (`T | null`), and keeping them as small...