Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@chiragrupani/karma-chromium-edge-launcher
Advanced tools
A Karma plugin. Launcher for different Chromium Edge channels - Dev, Canary, Beta and Stable
Launcher for Chromium Edge Canary, Dev, Beta and Stable channels for Windows OS, Mac OS and Linux OS
Available in NPM Registry
Install the package as dev-dependency
npm i -D @chiragrupani/karma-chromium-edge-launcher
Update Karma.conf.js
replace or append to array of browsers and add require plugin as below:
// karma.conf.js
module.exports = function (config) {
config.set({
- browsers: ['Chrome'],
+ browsers: ['Edge'],
plugins: [
- require('karma-chrome-launcher'),
+ require('@chiragrupani/karma-chromium-edge-launcher'),
],
});
};
Following browser channels are supported, add corresponding string in browsers:
If you want to launch browser in headless mode, below is correspondling list:
EdgeAny and EdgeAnyHeadless launches the first available channel from Canary, Dev, Beta and Stable in the order.
If you want to explicity specify the path for browser installation, set environment variable from this list, corresponding to release channel:
EDGE_BIN, EDGE_BETA_BIN, EDGE_DEV_BIN, EDGE_CANARY_BIN, EDGE_ANY_BIN
Example:
# Add at top of karma.conf.js
process.env.EDGE_DEV_BIN =
"C:\\Program Files (x86)\\Microsoft\\Edge Dev\\Application\\msedge.exe";
That's all is required to use Karma with Chromium Edge browser.
The browser can also be specified with npm test
commmand like below:
"coverage": "ng t --no-watch --code-coverage --reporters=junit,coverage-istanbul --browsers=EdgeHeadless --progress=false"
For running in docker, you may get error like below:
"Edge Headless stderr: [0116/032919.925976:ERROR:zygote_host_impl_linux.cc(90)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180."
Then you need to run it as non-root user or disable sandbox. Please read sandbox design before disabling it.
This can be done using custom launcher in karma.conf.js
using Edge launcher as base and adding extra flags as desired.
For example, for angular app, add below in karma.conf.js
:
customLaunchers: {
EdgeHeadlessCI: {
base: "EdgeAnyHeadless",
flags: ["--no-sandbox"],
},
},
and in package.json
use it like: "test:edge": "ng test --no-watch --browsers=EdgeHeadlessCI"
In case if you want to build package from github source
# Clone/download the package
# Run in clonned directory to install dependencies
npm install
# Run in clonned directory
npm run package # Generates package in tgz format
# Run in angular project
# Provide path to tgz file generated in earlier step
npm install -g <path/to/tgz>
The project is based on karma-chrome-launcher as most of flags/configs for Chromium Edge are similar to Chrome browser
For more information on Karma see the homepage.
FAQs
A Karma plugin. Launcher for different Chromium Edge channels - Dev, Canary, Beta and Stable
We found that @chiragrupani/karma-chromium-edge-launcher demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.