Fix npm deprecation warnings

Description

npm WARN deprecated opn@6.0.0: The package has been renamed to `open`
npm WARN deprecated material-ui@0.20.2: You can now upgrade to @material-ui/core
npm WARN deprecated os-homedir@2.0.0: This is not needed anymore. Use `require('os').homedir()` instead.
npm WARN deprecated cross-spawn-async@2.2.5: cross-spawn no longer requires a build toolchain, use it instead
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated core-js@1.2.7: core-js@<2.6.8 is no longer maintained. Please, upgrade to core-js@3 or at least to actual version of core-js@2.

Contributor guide

Tech stack

javascriptnodejselectron

Domain

desktop

Issue type

chore

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-3 hours

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

Basic npm knowledgeUnderstanding of package.json

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

85

Research direction

Examine the list of deprecation warnings in the issue body. For each deprecated package (e.g., opn, material ui), find its usage in package.json and replace it with the suggested alternative (e.g., use 'open' for opn, '@material ui/core' for material ui, etc.). Update the version ranges accordingly and run npm install to verify no warnings remain. Check if any of the replacements introduce breaking changes by reviewing the new packages' documentation or migration guides. The repository is webtorrent desktop, an Electron based app, so ensure the updates are compatible with Electron environment. Consider checking the comments on the issue for any additional guidance from maintainers.