Our great sponsors
-
That looks like a generic front-end error for when the back-end is unavailable, the back-end error should be more informative, but I don't know where exactly you can find it. At this point it might make sense to open an issue on the issue tracker of IHaskell, they will be able to give you more useful answers.
-
You could look into jupyterWith. With that you can list the packages you want to use in a shell.nix file; based on this file an environment is created in which Jupyter is run. I've also had issues with using packages with regular IHaskell in the past, but jupyterWith works pretty well for me.
-
Scout APM
Less time debugging, more time building. Scout APM allows you to find and fix performance issues with no hassle. Now with error monitoring and external services monitoring, Scout is a developer's best friend when it comes to application development.
-
Related posts
- Status of GHC on Apple M1 hardware?
- Most braindead easy end to end haskell workflow?
- Yet another (sic) Haskell project template with Nix, Docker, Lorri, and haskell-language-server
- Can't get things to work. It is normal to learn haskell with plain vim?
- Best UI Toolkit for generating UI elements at runtime