Jitsi-meet "make" takes a long time to complete

Kind of new to the area. Hope this is the right forum and right question.

We are planning to make some customizations to jitsi-meet site, following the instructions in README file, we found the “make” process takes very long time (minutes) to complete.

I wonder how do people usually make changes to jitsi-meet? We don’t need to run make in order to test every single change right?


You can run weback-dev server, which will load UI locally (https://localhost:8080) and use everything else from some deployment (beta.meet.jit.si by default). Use this command to run it against your deployment:
WEBPACK_DEV_SERVER_PROXY_TARGET="https://your.deployment.net" node_modules/.bin/webpack-dev-server
And then load https://localhost:8080, whenever you change js code the page will reload. Mind that this doesn’t monitor css, you need to run make deploy-css on every css change and reload.


Thanks a lot damencho! Just realized this is also mentioned in the README.

https://github.com/jitsi/jitsi-meet#running-with-webpack-dev-server-for-development, basically:
export WEBPACK_DEV_SERVER_PROXY_TARGET=https://your-example-server.com make dev

how can i do that? …

By executing make deploy-css

1 Like