</>PackageGraphPackageGraph

electron-to-chromium

npmv1.5.423

Provides a list of electron-to-chromium version mappings

Safe to adopt

Yes — electron-to-chromium scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 2 days ago. 50 releases in the last 2 years.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • AMaintenance: grade A, Excellent.

    Last published 2 days ago. 50 releases in the last 2 years.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 196 KB installed.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    ISC — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding electron-to-chromium to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

196 KB
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
No constraint declared
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the electron-to-chromium README.

jsFull README ↗
var e2c = require('electron-to-chromium');

electron-to-chromium vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
electron-to-chromiumthis page02ISC2 days ago
puppeteer-core02Apache-2.01 day ago
jose02MIT1 day ago

Dependencies

Declared by electron-to-chromium v1.5.423. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (5)

ava ^7.0.0compare-versions ^6.1.1node-fetch ^3.3.2nyc ^18.0.0shelljs ^0.10.0

Used by

Popular packages that depend on electron-to-chromium.

browserslistnpm

Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-env-preset

↓ 170.7M/wk◈ 5 dependents⚖ MITTS
@babel/compat-datanpm

The compat-data to determine required Babel plugins

↓ 0/wk◈ 1 dependents⚖ MIT

Relationship graph

Dependencies (left) and dependents (right) of electron-to-chromium.

browserslist@babel/compat-dataelectron-to-chrom…
electron-to-chromium dependencies dependents

Frequently installed together

caniuse-litenpm

A smaller version of caniuse-db, with only the essentials!

↓ 176.2M/wk◈ 3 dependents⚖ CC-BY-4.0
node-releasesnpm

Node.js releases data

↓ 164.1M/wk◈ 1 dependents⚖ MIT
baseline-browser-mappingnpm

A library for obtaining browser versions with their maximum supported Baseline feature set and Widely Available status.

↓ 0/wk◈ 4 dependents⚖ Apache-2.0TS
update-browserslist-dbnpm

CLI tool to update caniuse-lite to refresh target browsers from Browserslist config

↓ 0/wk◈ 1 dependents⚖ MITTS

Release history

50 releases in the last two years, typically about 1 day apart.

Recent versions of electron-to-chromium
VersionPublishedSizeLicense
1.5.423latest2 days ago196 KBISC
1.5.4226 days ago196 KBISC
1.5.4216 days ago195 KBISC
1.5.4208 days ago195 KBISC
1.5.4198 days ago195 KBISC
1.5.4189 days ago195 KBISC
1.5.41710 days ago195 KBISC
1.5.41613 days ago194 KBISC
1.5.41515 days ago194 KBISC
1.5.41416 days ago194 KBISC
1.5.41316 days ago194 KBISC
1.5.41220 days ago194 KBISC
1.5.41122 days ago193 KBISC
1.5.41022 days ago193 KBISC
1.5.40923 days ago193 KBISC

Overview

electron-to-chromium is an npm package that provides a list of electron-to-chromium version mappings. It has 2 known dependents in the graph. The latest version is 1.5.423, released under the ISC license.

Who should use it

Teams working in the npm ecosystem who need provides a list of electron-to-chromium version mappings and value a focused solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Clear open-source license (ISC).

Cons

  • No bundled TypeScript types (may require a separate @types package).

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

kilianvalkhof

Keywords

browserlistbrowserslistchromechromiumelectron

Frequently asked questions

Should I use electron-to-chromium?

Yes — electron-to-chromium scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 2 days ago. 50 releases in the last 2 years.

How do I install electron-to-chromium?

Run `npm install electron-to-chromium` to add electron-to-chromium to your npm project.

What license is electron-to-chromium released under?

electron-to-chromium is distributed under the ISC license.

How popular is electron-to-chromium?

npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on electron-to-chromium.

Is electron-to-chromium still maintained?

The most recent release of electron-to-chromium (v1.5.423) was published 2 days ago.

Does electron-to-chromium run install scripts?

No. electron-to-chromium does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.