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

After run calling localhost:5432 there is a white page #36

Open
MauGal opened this issue Apr 10, 2023 · 6 comments
Open

After run calling localhost:5432 there is a white page #36

MauGal opened this issue Apr 10, 2023 · 6 comments

Comments

@MauGal
Copy link

MauGal commented Apr 10, 2023

After pip and run, in localhost:5432 I have a white page, only title in tab report OpenPlayground.
I open developer tool and in console I have this error message:

Failed to load module
script: Expected a JavaScript module script but the server responded with a MIME type of "text/plain". Strict MIME type checking is enforced for module scripts per HTML spec.
errore-openplayground 2023-04-10 173808

@AlexanderLourenco
Copy link
Collaborator

Is this after running openplayground run?
Any errors in the console?

@MauGal
Copy link
Author

MauGal commented Apr 11, 2023

yes, I run with openplayground run.
In console there aren't errors.
errore-openplayground 2023-04-11 084908

@sbaglieri
Copy link

sbaglieri commented Apr 11, 2023

Same issue here
image
OS: Win10
Python -v 3.11.3

@AlexanderLourenco
Copy link
Collaborator

@sbaglieri @MauGal could you try pip installing the latest package?

@MauGal
Copy link
Author

MauGal commented Apr 14, 2023

@AlexanderLourenco I have upgraded package (openplayground version 0.1.5) and I have the same issue.
Same error in developer console on index.d826928d.js.
No error in terminal console
My OS is Win 11 and python version 3.11.0

I have tried to uninstall and reinstall but nothing, it's equal.

@Terristen
Copy link

Terristen commented May 1, 2023

Same issue, Windows 11 Python 3.10.11

Edit: Information from Chrome DevTools

A page or script is accessing at least one of navigator.userAgent, navigator.appVersion, and navigator.platform. Starting in Chrome 101, the amount of information available in the User Agent string will be reduced.
To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData.
Note that for performance reasons, only the first access to one of the properties is shown.

Edit 2:
This appears to be something in the React framework having to do with relative pathing of files and/or pointing to files that are not on your main path. I suspect something to do with where the server folder is deployed (maybe in the user's account folder structure) is not playing well with React. (I'm not a React dev, so I'm basing this off initial Google-Fu.)

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

No branches or pull requests

4 participants