You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@forkifable-splitter is compatible with Fable 2 so I don't think you need to change it as we did for the webpack config when switching from Fable 1 to Fable 2.
For example, for a node cli apps this config is enough.
First, I would try to update all the npm packages to their latest version or at least thus related to Fable compilation. You will also need to add fable-compiler (related to Fable 2.1 release).
Activity
MangelMaxime commentedon Feb 11, 2019
I think you first need to update fable-react-native for Fable 2 supports.
MangelMaxime commentedon Feb 20, 2019
@forki
fable-splitteris compatible with Fable 2 so I don't think you need to change it as we did for the webpack config when switching from Fable 1 to Fable 2.For example, for a node cli apps this config is enough.
As you can, see it's almost empty.
First, I would try to update all the npm packages to their latest version or at least thus related to Fable compilation. You will also need to add
fable-compiler(related to Fable 2.1 release).forki commentedon Feb 20, 2019
do we continue to use dotnet-fable nuget package? Probably not, right?
forki commentedon Feb 20, 2019
do I use some yarn command?
WIP at #66
MangelMaxime commentedon Feb 20, 2019
dotnet-fablehas been removed since Fable 2.1The replacement is to use
fable-compilerfrom npm.To set up Fable 2.1:
yarn upgrade fable-splitter@latest fable-compiler@latestdotnet-fablefrompaket.dependenciesandpaket.referenceforki commentedon Feb 20, 2019
yes I have fable-compiler installed. but how to start it!?