back to home

wireapp / wire-webapp

👽 Wire for web

1,185 stars
305 forks
18 issues
TypeScriptLessJavaScript

AI Architecture Analysis

This repository is indexed by RepoMind. By analyzing wireapp/wire-webapp in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.

Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.

Source files are only loaded when you start an analysis to optimize performance.

Embed this Badge

Showcase RepoMind's analysis directly in your repository's README.

[![Analyzed by RepoMind](https://img.shields.io/badge/Analyzed%20by-RepoMind-4F46E5?style=for-the-badge)](https://repomind.in/repo/wireapp/wire-webapp)
Preview:Analyzed by RepoMind

Repository Overview (README excerpt)

Crawler view

Wire™ This repository is part of the source code of Wire. You can find more information at wire.com or by contacting opensource@wire.com. You can find the published source code at github.com/wireapp/wire. For licensing information, see the attached LICENSE file and the list of third-party licenses at wire.com/legal/licenses/. If you compile the open source software that we make available from time to time to develop your own mobile, desktop, or web application, and cause that application to connect to our servers for any purposes, we refer to that resulting application as an "Open Source App". All Open Source Apps are subject to, and may only be used and/or commercialized in accordance with, the Terms of Use applicable to Wire Application, which can be found at https://wire.com/legal/#terms. Additionally, if you choose to build an Open Source App, certain restrictions apply, as follows: a. You agree not to change the way the Open Source App connects and interacts with our servers; b. You agree not to weaken any of the security features of the Open Source App; c. You agree not to use our servers to store data for purposes other than the intended and original functionality of the Open Source App; d. You acknowledge that you are solely responsible for any and all updates to your Open Source App. For clarity, if you compile the open source software that we make available from time to time to develop your own mobile, desktop, or web application, and do not cause that application to connect to our servers for any purposes, then that application will not be deemed an Open Source App and the foregoing will not apply to that application. No license is granted to the Wire trademark and its associated logos, all of which will continue to be owned exclusively by Wire Swiss GmbH. Any use of the Wire trademark and/or its associated logos is expressly prohibited without the express prior written consent of Wire Swiss GmbH. Monorepo Layout • : client (Webpack/React) plus E2E tests and i18n files • : node/express wrapper that serves the built webapp and handles proxying • : package - centralized environment configuration management with type-safe configuration loading and validation • : package - Wire's communication core library handling authentication, WebSocket connections, and protocol messaging • Root-level tooling ( , Nx, bin scripts) orchestrates both apps and libraries The root and scripts are the entry points; package-level scripts delegate to them. How to Build the Open Source Client Prerequisites: • Install Node.js • Install Yarn • Install Dependencies & Fetch Configuration • Run (uses Yarn 4 workspaces) • This will install all dependencies and run (via root ). • uses to select a config repository version ( or ), then copies: • config content into • into repository root • Runtime priority is: process environment (for example AWS) > > > code fallback. • Build & Run Development • Copy to to override/extend defaults • Add the following entries to your hosts file (macOS / Linux: , Windows 10: ): • (to connect with the staging backend) • (to connect with the imai backend) • Run to build static assets • Run (runs ); the app will be available at https://local.zinfra.io:8081/auth/ Install Self-Signed Certificate If you would like your browser to trust the certificate from "local.wire.com"/"local.zinfra.io"/"local.imai.wire.link": • Download mkcert - Installation on Mac: (refer to the latest README.md) • Set the environment variable to • Run Environment Configuration The application can be configured to connect to different environments by modifying the following environment variables in your file: For the full environment variable reference, see Environment Variables. **Staging:** **Imai:** **Local:** After updating the environment variables, the app will be available at the corresponding URL. Production • Build and package for production: (or ) • This builds both the server and webapp (in production mode) and creates the deployment package at • Start the server output from (or build a Docker image with ) **Note:** The command has been deprecated. Packaging is now integrated into the build process via or . Testing To launch the full test suite: Other useful tasks: • Lint: • Type-check: • E2E (Playwright): CI Status Translations All Wire translations are crowdsourced via Crowdin. Add New Strings **Info:** • To download translations we use Crowdin API v1, and you need to set up your username and api_key (Account API key) • To upload translations we use Crowdin CLI v3, and you will need to set up project_identifier and api_token (Personal Access Token) **Setup:** Create a in this repository and add the following entries: **Usage:** • Add a string variable to "i18n/en-US.json" • Create a PR and merge it after approval. When the PR gets merged, our CI will take care of uploading the English texts to Crowdin If our CI pipeline is broken, you still have the option to upload new strings manually. For this case, do the following: • Install Crowdin CLI v3 • Verify you have a in place • Run Once translations are uploaded on Crowdin, our (and external) translators can translate the new strings on Crowdin. There is a script that will run to create PRs with translation updates. As an alternative, translations can be downloaded in the following way: • Verify your string shows up on the Crowdin project: wire-webapp • Add a translation on Crowdin • Approve the translation on Crowdin • Run Contributing Contributions are welcome! Feel free to check our issues page. The following commits will help you get started quickly with our code base: • Show a modal / pop-up • Sync setting between via backend