Thank you for your comment.
Yes I am learning Elm and I am aware of the elm init, create-elm-app (if this is what you meant by elm-app) and elm-live.
Here I wanted a very lightweight setup that will give me a nice development experience.
elm init would mean manually compiling each time.
elm-live - manually refreshing the page.
create-elm-app - setting up a lot of things that I don't need.
So I decided to go for parcel-bundler - zero config, automatically setting up the Elm project and giving me a development server + hot module reload.
Regarding elm-ui - I am planning to dig into it deeper, but for this small project I wanted to be focused on more Elm core things. I am thinking of eventually converting this project to use elm-ui, but not just now.
I went with the parcel as well. But I have an empty page. If I have an error in the compiler the parcel tells me about it. So that means it's working. But the page is still empty.
A note on elm-live. You don't have to manually update the page it is automatic.
Sorry to hear the Parcel didn't work for you.
It is hard to understand what is wrong without seeing your code. Can you share it so I can take a look?
Also, you're right about the elm-live. My mistake.
Actually, it works. I figured what the problem was. The problem was with my Russian government blocking the Elm. Parcel wanted to download some packages. I turned on vpn and it worked.
I knew there was something strange about it. Because the code didn't have a mistake. And when I for example purposefully introduce a mistake the parcel/elm would show it to me in the browser.
It's great you figured that out!
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.