
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).
grunt-continue
Advanced tools
A grunt plugin to force other tasks to continue after failures
Inspired by and extended from this answer by explunit on StackOverflow
Install next to your project's Gruntfile.js with:
$ npm install grunt-continue
Here is a simple example gruntfile to show how you might force grunt to continue after failing tests if you have some cleanup that you need to perform afterward
module.exports = function(grunt) {
// Add the grunt-continue tasks
grunt.loadNpmTasks('grunt-continue');
// Other tasks and configuration
...
grunt.registerTask('default', [
'setup',
'continueOn',
// All tasks after this point will be run with the force
// option so that grunt will continue after failures
'test',
'continueOff',
// Tasks after this point will be run without the force
// option so that grunt exits if they fail
'cleanup'
]);
};
continueOff
does not turn off the continuing if --force
was specified at the command line.
If continueOn
is called muliple times continueOff
must be called that many times in order to stop continuing.
If continueOff
is called more times than continueOn
it will fail.
It is sometimes useful to check if there were any warnings issued by any tasks within continueOn
and continueOff
.
For example, you may run a test within the block and cleanup at the end. In this instance you want the overall build to fail after the cleanup.
To accommodate this add the following task at the end:
module.exports = function(grunt) {
// Add the grunt-continue tasks
grunt.loadNpmTasks('grunt-continue');
// Other tasks and configuration
...
grunt.registerTask('default', [
'setup',
'continueOn',
// All tasks after this point will be run with the force
// option so that grunt will continue after failures
'test',
'continueOff',
// Tasks after this point will be run without the force
// option so that grunt exits if they fail
'cleanup',
'continueFailIfWarningsWereIssued'
]);
};
grun
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using:
$ npm test
To use the Vagrantfile you will also need to install the following vagrant plugins
$ vagrant plugin install vagrant-omnibus
$ vagrant plugin install vagrant-berkshelf
Copyright © 2013 Peter Halliday
Licensed under the MIT license.
FAQs
A grunt plugin to force other tasks to continue after failures
The npm package grunt-continue receives a total of 4,898 weekly downloads. As such, grunt-continue popularity was classified as popular.
We found that grunt-continue 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.