brave/brave-browser

JSON file containing all installed addons available to export/import?

Open

#48,166 opened on Aug 5, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (2,164 forks)batch import
OS/Desktopfeature-requestfeature/extensionshelp wantedpriority/P5suggestion

Repository metrics

Stars
 (16,194 stars)
PR merge metrics
 (Avg merge 10h 44m) (21 merged PRs in 30d)

Description

Platforms

Linux, Windows

Description

I have been using Brave browser for so long (both on mobile, Android, and on desktop, Windows and Linux) on different machines (laptop and desktop).

I noticed that keeping synchronized addons (install/uninstall) between different computers is quite time-consuming task, especially if you have a lot of addons installed.

Therefore, having JSON file would come in handy: export it from one machine and import into another.

The process should be:

  • put in on (C:\Users\[USER]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Brave Apps) path;
  • let Brave parse it comparing local file addons with imported file addons; if an extension is not installed or not up-to-date or dismissed, it would simple download/remove it automatically, without any manual action needed by user.

Anything like that available right now?

Contributor guide

Research direction
Investigate how Brave stores extension data (e.g., in profile directory) and implement a feature to export installed addons to a JSON file and import from such a file, handling installation, updates, and removals automatically.
Tech stack
javascript
Domain
desktopmobile
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75