-
Notifications
You must be signed in to change notification settings - Fork 301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compilations errors with .NET 7 & Fable 3.0.1 #3278
Comments
Thanks a lot for the detailed report @OkayX6! Yes, unfortunately dotnet sdk 7 is giving problems. We've almost fixed it for the incoming Fable 4 (see #3279) but I'm not sure if we'll be able to patch it for Fable 3. Can you please try upgrading to Fable 4? You should be able to upgrade any Feliz app with just two commands: dotnet tool install fable --prerelease
# In your project directory
dotnet add package Feliz.CompilerPlugins --prerelease |
Just want to add that it also fails with Fable 2 but in a different way. This is from fable2-samples/nodejs with .net sdk 7.0.100
|
@OkayX6, @harvito {
"sdk": {
"version": "6.0.100",
"rollForward": "latestFeature"
}
} You'll also need the older version of sdk (e.g. dotnet 6) installed besides dotnet 7. They can coexist just fine. |
Thanks @pkese for your tips!
Thanks @alfonsogarciacaro, it worked. (By the way, It broke my webpack config, my Node ENV VARS stopped working) |
@OkayX6 Happy yo hear it worked for you! Did you upgrade from Fable 2 or 3? In Fable 2 Webpack called Fable but since Fable 3 it is the other way around, maybe this caused by the issue with the env cars. |
Upgraded from Fable 3 :) |
Thanks for the global.json tip, this is working with Fable compiler 2. Will upgrade to 4 once it's GA. |
Description
Working project doesn't compile anymore with Fable 3.0.1.
Fable 3.7 simply hangs.
Repro code
Any Fable project. Try with Feliz template
dotnet new feliz -n AwesomeApp
Expected and actual results
Expected results is that it compiles.
Actual results:
Related information
The text was updated successfully, but these errors were encountered: