-
Notifications
You must be signed in to change notification settings - Fork 19
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
Bulma Intellisense error: Fable.React
does not contain ReactElement
#133
Comments
@mrakgr Hum, this is looks like a error related to he fact that you are using Fable.React 9 with a version of Feliz or Feliz.Bulma which doesn't support Fable.React 9. You can either manually revert to Fable.React 8, Feliz 1, Feliz.Compiler 1, etc. Or try to use Feliz 2, the pre release version of Feliz.Bulma 2. Note that if you use Feliz 2, you need to use Fable 4 prerelease. |
Updating Fable to the prerelease is easy using |
I tried putting this in, but it doesn't seem like the version is changing. |
This is indeed the correct of doing it. Did you run You can also check in your |
|
For Feliz, it is normal your version didn't change because this is already the latest version. For Feliz.Bumla, I suspect that this is because the name of the version is not standard... You can pin the version your self manually. You will need to relax your Fsharp.Core restriction because Feliz.Bumla require Fsharp.Core v7.
|
I see, I could have just used this to check the versions. Yeah, it works now. Thank you. |
Your welcome, I sent a PR trying to make Feliz.Bulma ready for stable version #134 |
In Visual Studio, I get
The module/namespace 'Fable.React' from compilation unit 'Fable.React' did not contain the namespace, module or type 'ReactElement'
whenever I try to autocomplete Bulma. In Visual Studio Code, I get this at the top of the module.The project compiles fine despite this using
dotnet run
.What do I do about this? It might be due to me upgrading all the packages to the latest, but if so, I'd rather not resolve it by downgrading.
The text was updated successfully, but these errors were encountered: