Home
Docs
GitHub
Pricing
Blog
Log In

Run Sandworm Audit for your App

Get started
Hold on, we're currently generating a fresh version of this report
Generated on Apr 1, 2024 via pnpm

electron-to-chromium 1.4.648

Provides a list of electron-to-chromium version mappings
Package summary
Share
0
issues
1
license
1
ISC
Package created
15 Jan 2017
Version published
26 Jan 2024
Maintainers
1
Total deps
1
Direct deps
0
License
ISC

Issues

0
This package has no issues

Licenses

ISC License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
Cannot
hold-liable
Must
include-copyright
include-license
1 Packages, Including:
electron-to-chromium@1.4.648
Disclaimer

This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.

Sandworm is not a law firm and does not provide legal services. Distributing, displaying, or linking to this deed or the license that it summarizes does not create a lawyer-client or any other relationship.

Direct Dependencies

0
All Dependencies CSV
β“˜ This is a list of electron-to-chromium 's direct dependencies. Data on all dependencies, including transitive ones, is available via CSV download.
NameVersionSizeLicenseTypeVulnerabilities

Visualizations

Frequently Asked Questions

What does electron-to-chromium do?

The electron-to-chromium npm package, developed by Kilian Valkhof, delivers a critical role in providing a host of mappings between Electron versions and the Chromium versions they use. With this functionality, other tools in the web development and JavaScript ecosystem - such as Browserslist, Autoprefixer, Stylelint, babel-preset-env, and eslint-plugin-compat - can efficiently resolve specific Electron version strings to their equivalent Chromium versions. This feature is rather beneficial for developing software that needs to accurately understand the specific capabilities of the underlying web rendering engine.

How do you use electron-to-chromium?

To utilize electron-to-chromium, first install it via npm by npm install electron-to-chromium. After installation, include Electron-to-Chromium in your project using require:

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

The package provides various properties like versions, fullVersions, chromiumVersions, fullChromiumVersions to get the corresponding major or full Chromium version for a given Electron version. You can also use the functions electronToChromium() and chromiumToElectron() for mapping between Electron and Chromium versions.

Code usage examples include:

var chromeVersion = e2c.electronToChromium('1.4'); // returns "53"
var electronVersion = e2c.chromiumToElectron('54'); // returns "1.4"

To retrieve just the versions, you can require individual lists:

var versions = require('electron-to-chromium/versions');

Please keep in mind that the electronToBrowserList() function has been deprecated as Browserslist now includes electron-to-chromium.

Where are the electron-to-chromium docs?

Documentation for electron-to-chromium can be found in its official repository on GitHub. On the README page, users can find comprehensive instructions on how to install, use, and update the program and it also offers handy code examples that illuminate default usage for developers.