-
Notifications
You must be signed in to change notification settings - Fork 96
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
Node version compatibility of the client side and creation of the docker container. #83
Comments
@serhatoral What you mean? It works fine for me on node.js v20.9.0. |
@yarikpetrenko I was getting errors when I tried to run it using Node 14.21.3 and npm versions higher than 6.14.18. I'm getting errors related to the sass library. |
@serhatoral Now I get it.... You are speaking about client side. Yeah I can see that ui uses some old packages but there is also a Dockerfile inside ui folder so you can setup everything with docker I guess. Also if you want to just serve client side not edit you can use any web server or even just double click index.html inside ui/dist as it says in README. I use 'Live Server' extension for VSCode for convenience. |
@yarikpetrenko You're right, I should have mentioned that the problem is on the client 🙂 |
thanks serhat. |
I'm investigating the build issues. |
Hello. Using an old Node.js 14.x version definitely helps to get ride of most errors (sass, One babel related problem around the support of underscores in numbers still undermines the
|
Running client(ui folder) in localhost
You can access the working version of the client side (ui folder) from this repository .
This project doesn't support Node versions higher than 14.21.3 and npm versions higher than 6.14.18 . Is not compatible with higher versions of sass library. You should downgride Node version on your computer. You can easily do this by using nvm as fallows;
Finally, you can run the project using
npm install
andnpm run serve
Docker container
To create a docker container, you can update the dockerfile file as in this pull-request and add the nginx.conf file.
The text was updated successfully, but these errors were encountered: