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.
jest-watcher
Advanced tools
The jest-watcher package is a part of the Jest ecosystem and is used to implement custom watch plugins for Jest. It provides an API to create plugins that can hook into Jest's watch mode, allowing developers to add custom watch behaviors to their test suites.
Custom Watch Plugins
This feature allows developers to create custom watch plugins that can react to file changes, determine if a test suite should run, and more. The code sample shows a basic structure of a custom watch plugin.
class MyCustomPlugin {
apply(jestHooks) {
jestHooks.onFileChange(({ projects }) => {
console.log('Files changed:', projects[0].changedFiles);
});
jestHooks.shouldRunTestSuite(() => true);
}
}
module.exports = MyCustomPlugin;
Interactive Watch Plugins
This feature allows the creation of interactive watch plugins that can provide custom interactive CLI interfaces during Jest's watch mode. The code sample demonstrates how to implement an interactive behavior that filters tests based on a pattern.
class MyInteractivePlugin {
run(globalConfig, updateConfigAndRun) {
// Implement interactive behavior here
updateConfigAndRun({
testNamePattern: 'pattern to filter tests'
});
return Promise.resolve();
}
}
module.exports = MyInteractivePlugin;
Mocha-watch is a watch mode for Mocha testing framework. It provides similar functionality to jest-watcher by re-running tests when file changes are detected. However, it is tailored for Mocha and does not offer the same plugin API for extending watch behavior.
Karma is a test runner that works with multiple testing frameworks like Jasmine, Mocha, and QUnit. It can watch files and re-run tests on changes, similar to jest-watcher. Karma is more of a full-fledged test runner with a focus on running tests in different browsers, whereas jest-watcher is specifically for creating watch plugins in Jest.
AVA is a test runner with built-in watch mode functionality. It automatically re-runs tests when it detects changes. AVA's watch mode is not plugin-based like jest-watcher, but it offers a simple and fast out-of-the-box solution for watching tests without the need for additional configuration.
29.7.0
[create-jest]
Add npm init
/ yarn create
initialiser for Jest projects (#14465)[jest-validate]
Allow deprecation warnings for unknown options (#14499)[jest-resolver]
Replace unmatched capture groups in moduleNameMapper
with empty string instead of undefined
(#14507)[jest-snapshot]
Allow for strings as well as template literals in inline snapshots (#14465)[@jest/test-sequencer]
Calculate test runtime if perStats.duration
is missing (#14473)[@jest/create-cache-key-function]
Cache access of NODE_ENV
and BABEL_ENV
(#14455)[jest-cli]
Move internal config initialisation logic to the create-jest
package (#14465)FAQs
Delightful JavaScript Testing.
The npm package jest-watcher receives a total of 21,961,215 weekly downloads. As such, jest-watcher popularity was classified as popular.
We found that jest-watcher demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 5 open source maintainers 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.