Closed 1aristotelis closed 1 year ago
yeah it happens sometimes this is not specific to the watch page. I think it has to do with the network load on the client side. refreshing the page usually fixes the issue
Oh yes, you are right. Upon refresh, the page now looks like this. Much better! Very exciting. I am eager to see this merged and deployed to production.
This builds for me, but I have to use
--force
when doingnpm install
Then when I
npm run dev
it deploys to localhost and I navigated to the new watch page, and it looks like this:What do you think?