wulkano/kap

Migrate to `@electron/remote`

Open

#1089 opened on Feb 5, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (11,043 stars) (548 forks)batch import
Help WantedPriority: HighType: Enhancement

Description

It blocks us from upgrading Electron and we're left on an old Electron version...

https://github.com/electron/remote/blob/main/README.md#migrating-from-remote

Contributor guide

Tech stack
javascript
Domain
desktop
Issue type
chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
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
Electron basicsJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue aims to migrate from the deprecated 'remote' module to '@electron/remote' to allow upgrading Electron. It references the official migration guide at https://github.com/electron/remote/blob/main/README.md#migrating from remote. The repository is a screen recorder built with Electron, so the migration likely involves updating imports and usage patterns across the codebase. No assignees, linked PRs, or recent comments indicate the work is available but requires familiarity with Electron's remote module and the migration steps.