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

Website pitsby demo is empty #31

Open
m-cisse-easy-live opened this issue Sep 27, 2024 · 5 comments
Open

Website pitsby demo is empty #31

m-cisse-easy-live opened this issue Sep 27, 2024 · 5 comments

Comments

@m-cisse-easy-live
Copy link

Hello,

I installed the repository and followed the instructions below to generate a build of the demo :

  • rm -rf ./node_modules
  • npm i
  • rm -rf ./dist
  • npm run build
  • npm run docs

And when I launch the application with serve (command: cd docs/ && serve .) then my page is empty and in console I get this :
image

My environment :

  • node 18.17.1
  • npm 9.6.7
  • Windows 10
@rafaelcamargo
Copy link
Member

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
Tip: To handle multiple versions of Node, I use NVM

The environment that works for me is:

  • Node 16.20.2
  • NPM 8.19.4
  • Mac Ventura 13.5

Let me know if it works for you 🙏

@m-cisse-easy-live
Copy link
Author

m-cisse-easy-live commented Sep 30, 2024

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 Tip: To handle multiple versions of Node, I use NVM

The environment that works for me is:

  • Node 16.20.2
  • NPM 8.19.4
  • Mac Ventura 13.5

Let me know if it works for you 🙏

Hello @rafaelcamargo,

Fine and you ?
Sorry for the late reply.

I tried with the following configuration:

  • Node 16.20.2
  • NPM 8.19.4
  • Windows 10

Do you think I should try it on a Linux environment?

@rafaelcamargo
Copy link
Member

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.

@m-cisse-easy-live
Copy link
Author

m-cisse-easy-live commented Oct 1, 2024

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.

@rafaelcamargo
Copy link
Member

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 cross-env that might fix the issues between operating systems. If I get a Windows machine, I'll try to do some tests with it.

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

2 participants