Skip to content
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

The "Blog" demo app doesn't work #9892

Closed
firasrg opened this issue Jun 2, 2024 · 5 comments · Fixed by #9900
Closed

The "Blog" demo app doesn't work #9892

firasrg opened this issue Jun 2, 2024 · 5 comments · Fixed by #9900

Comments

@firasrg
Copy link

firasrg commented Jun 2, 2024

I'm trying to see the Blog demo.

What you were expecting:
I'm expecting that the demo works fine as it's made by you.

What happened instead:
Blank page at start :
image

Steps to reproduce:
none

@fzaninotto
Copy link
Member

I can't reproduce the problem: The demo does start (although after a good 30s).

Can you please add mode details about your browser and OS?

@firasrg
Copy link
Author

firasrg commented Jun 3, 2024

Thanks fot reply @fzaninotto. It seems the app in my side doesn't work even in more than that delay! However, even 30 seconds is too much. ive tried to reach it on stackblitz from Windows and smartphone with google chrome and got same result

@fzaninotto
Copy link
Member

Does https://codesandbox.io/p/devbox/github/marmelab/react-admin/tree/master/examples/simple work?

@firasrg
Copy link
Author

firasrg commented Jun 3, 2024

oh it does ! in that case i'd suggest to put this working example instead in docs :)

@fzaninotto
Copy link
Member

I suspect there has been a regression in Stackblitz lately, it didn't use to be this slow.

We prefer Stackblitz over CodSandbox because CodeSandbox now drastically restricts the number of sandboxes you can make with a free plan. So many developers can't create a repro without paying, which is something we want to avoid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants