
Research
/Security News
Critical Vulnerability in NestJS Devtools: Localhost RCE via Sandbox Escape
A flawed sandbox in @nestjs/devtools-integration lets attackers run code on your machine via CSRF, leading to full Remote Code Execution (RCE).
A Node module that adds colorful CLI support for the QUnit testing framework.
There are two ways to use qunit-cli:
Include it at the top of your test files. First, install the module using npm.
npm install qunit-cli
And now, require it in your test files:
if (typeof QUnit == 'undefined') // if your tests also run in the browser...
QUnit = require('qunit-cli');
// use QUnit as you normally would.
Note that this module does not introduce QUnit into the global scope like QUnit does in the browser, so you'll have to do that yourself if needed.
To run, use the node
program.
node mytests.js
Use the command-line testrunner located at bin/qunit-cli
, passing it the test files as arguments.
If you install the module globally using npm, you can use the qunit-cli
command which will be
installed into your PATH.
npm install qunit-cli -g
qunit-cli mytests.js
This will introduce QUnit into the global scope like QUnit does in the browser, so you don't need to modify the tests themselves. You can use both methods in the same test files without problems.
There are several command line options available when running your tests using qunit-cli that mimic some of the options in the standard browser-based QUnit testing interface. They are:
--module, -m Limits testing to an individual module
--test, -t Limits testing to a single test (by number)
--quiet, -q Flag to hide passed tests from the output
The command-line test runner has some additional options available:
--code, -c Path to code loaded globally. You can prefix a namespace
using a colon (:)
Here are some examples:
# code exports are added to global namespace
qunit-cli -c /path/to/code test.js
# code exports are added to ns namespace
qunit-cli -c ns:/path/to/code test.js
qunit-cli
is released under the MIT license.
FAQs
A command line interface for the QUnit testing framework
We found that qunit-cli demonstrated a not healthy version release cadence and project activity because the last version was released 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.
Research
/Security News
A flawed sandbox in @nestjs/devtools-integration lets attackers run code on your machine via CSRF, leading to full Remote Code Execution (RCE).
Product
Customize license detection with Socket’s new license overlays: gain control, reduce noise, and handle edge cases with precision.
Product
Socket now supports Rust and Cargo, offering package search for all users and experimental SBOM generation for enterprise projects.