Maxime Mangel

> I should have mentioned that I use Fable with the `outDir` option to put _transpilated_ files where they are meant to be, i. e. **outside** the _source_ directory (the...

@Freymaurer Can't you do like Nacara and have a `js` folder containing your native JavaScript files in your NPM packages? > @MangelMaxime maybe it would be possible to have a...

Hello @Freymaurer, I believe what you are looking for is `exportDefault`: > Makes an expression the default export for the JS module. Used to interact with JS tools that require...

Hum indeed, the problem is I don't think F# as a mechanism for re-exporting types from modules. So we will need a custom Fable syntax / code to cover this...

@Freymaurer Thank you for sharing the script

I have a difficult time seeing what would be the separations in term of features/API between the packages. I suppose for `Fable.Cli`, the pipeline would be something like: 1. You...

> Although if now MSBuild can export all we need as JSON, perhaps that's a good option too. This could remove the trick we do with creating a `.csproj` for...

Here is a summary of our discussion *@nojaf @jwosty Please feel free to complete or correct me* We want to continue the exploration of introducing "Fable as a library". Goals:...

Personally, I think `Fable.Compiler` is good enough for a name too. Like that you have: - `Fable.Ast` - `Fable.Cli` - `Fable.Compiler` - etc. And I believe each name is self...

This one is tricky. The problem comes from this function: ```js export function Inheritor_$reflection() { return class_type("Test.Inheritor", void 0, Inheritor, Base$1_$reflection(Inheritor_$reflection())); } ``` Which as you can see reference itself...