This is a preparation for electron 14+, where electron-store is no longer in a usable state (currently used version does not work due to remote module removed in electron 14, latest version extends every app startup to 10 seconds). Once sufficient migration period has passed, electron-store and redux-persist-electron-storage and the ipc call introduced here (electron-store-exists) can be removed.
|8 months ago|
|.github||1 year ago|
|app||8 months ago|
|resources||1 year ago|
|.eslintignore||1 year ago|
|.eslintrc.js||4 years ago|
|.flowconfig||3 years ago|
|.gitignore||4 years ago|
|.nvmrc||2 years ago|
|LICENSE||6 years ago|
|README.md||8 months ago|
|SECURITY.md||2 years ago|
|entitlements.mac.plist||2 years ago|
|linux-sandbox-fix.js||1 year ago|
|main.js||8 months ago|
|package-lock.json||8 months ago|
|package.json||8 months ago|
|screenshot.png||4 years ago|
|webpack.main.js||2 years ago|
|webpack.renderer.js||1 year ago|
Jitsi Meet Electron
- End-to-End Encryption support (BETA)
- Works with any Jitsi Meet deployment
- Builtin auto-updates
- ~Remote control~ (currently disabled due to security issues)
- Always-On-Top window
- Support for deeplinks such as
myroomon the configured Jitsi instance) or
myroomon the Jitsi instance running on
Download our latest release and you're off to the races!
|Windows||macOS||GNU/Linux (AppImage)||GNU/Linux (Deb)|
NOTE: The GNU/LInux builds are 64-bit only.
For macOS user, you can install the application using the following command:
brew install --cask jitsi-meet
Using it with your own Jitsi Meet installation
⚠️ The following additional HTTP headers are known to break the Electron App:
Content-Security-Policy "frame-ancestors [looks like any value is bad]"; X-Frame-Options "DENY";
A working Content Security Policy looks like that:
Content-Security-Policy "img-src 'self' 'unsafe-inline' data:; script-src 'self' 'unsafe-inline' 'wasm-eval'; style-src 'self' 'unsafe-inline'; font-src 'self'; object-src 'none'; base-uri 'self'; form-action 'none';";
If you want to hack on this project, here is how you do it.
Show building instructions
Install Node.js 12 first (or if you use nvm, switch to Node.js 12 by running
Extra dependencies for Windows
npm install --global --production windows-build-tools npm config set msvs_version 2017
Extra dependencies for GNU/Linux
X11, PNG and zlib development packages are necessary. On Debian-like systems then can be installed as follows:
sudo apt install libx11-dev zlib1g-dev libpng-dev libxtst-dev
Install all required packages:
Starting in development mode
The debugger tools are available when running in dev mode and can be activated with keyboard shortcuts as defined here https://github.com/sindresorhus/electron-debug#features.
It can also be displayed automatically from the
SHOW_DEV_TOOLS environment variable such as:
SHOW_DEV_TOOLS=true npm start
or from the application
--show-dev-tools command line flag.
Building the production distribution
npm run dist
Working with jitsi-meet-electron-utils
jitsi-meet-electron-utils is a helper package which implements many features such as remote control and the always-on-top window. If new features are to be added / tested, running with a local version of these utils is very handy, here is how to do that.
By default the jitsi-meet-electron-utils is build from its git repository sources. The default dependency path in package.json is:
To work with local copy you must change the path to:
To build the project you must force it to take the sources as
npm update will
not do it.
npm install jitsi-meet-electron-utils --force
NOTE: Also check the jitsi-meet-electron-utils README to see how to configure your environment.
A warning will show up mentioning the app is unsigned upon first install. This is expected.
On macOS Catalina a warning will be displayed on first install. The app won't open unless "open" is pressed. This dialog is only shown once. Builtin auto-updates are not yet handled in macOS due to unsigned build.
If after downloading it, you can't execute the file directly, try running
chmod u+x ./jitsi-meet-x86_64.AppImage
NOTE for old GNU/Linux distributions
You might get the following error:
FATAL:nss_util.cc(632)] NSS_VersionCheck("3.26") failed. NSS >= 3.26 is required. Please upgrade to the latest NSS, and if you still get this error, contact your distribution maintainer.
If you do, please install NSS (example for Debian / Ubuntu):
sudo apt-get install libnss3
The json files are for all the strings inside the application and can be translated here.
New translations require the addition of a line in index.js.
Apache 2. See the LICENSE file.
Jitsi is built by a large community of developers, if you want to participate, please join community forum.