-
Notifications
You must be signed in to change notification settings - Fork 2
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
Website pitsby demo is empty #31
Comments
Hi, @m-cisse-easy-live! How are you? I've just simulated your steps and I think I've found the issue. Try to change your Node version to 16.x The environment that works for me is:
Let me know if it works for you 🙏 |
Hello @rafaelcamargo, Fine and you ? I tried with the following configuration:
Do you think I should try it on a Linux environment? |
Hey, in fact, the only variable that seems different regarding the environment is Windows. Unfortunately, I don't have a machine with Windows to run some tests. However, as far as I know, Windows now has the ability to offer a Linux environment: https://learn.microsoft.com/en-us/windows/wsl/install. Have you tried this? I think it could be very helpful. |
I had a Linux Debian 11 server (bullseye) and it works fine. But when I ran the npm run build command, I got the error: ERR_OSSL_EVP_UNSUPPORTED and I had to activate the node option: export NODE_OPTIONS=--openssl-legacy-provider to run the npm run build command correctly. Update (02/10) : I tried on my Windows 10 environment with the export option NODE_OPTIONS=--openssl-legacy-provider and it still didn't work. I have the impression that the library is only supported in a Windows environment. |
Since I haven't ever tried to run this project on Windows, you're likely right, my friend. Some time ago, I heard about an npm package called |
Hello,
I installed the repository and followed the instructions below to generate a build of the demo :
And when I launch the application with serve (command:
cd docs/ && serve .
) then my page is empty and in console I get this :My environment :
The text was updated successfully, but these errors were encountered: