
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
grunt-rerun
Advanced tools

Launch, relaunch and stop grunt task.
This plugin requires Grunt ~0.4.0
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
npm install grunt-rerun --save-dev
One the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:
grunt.loadNpmTasks('grunt-rerun');
In your project's Gruntfile, add a section named rerun to the data object passed into grunt.initConfig().
grunt.initConfig({
rerun: {
yourtarget: {
options: {
tasks: ['express'],
keepalive: false,
port: 12456
},
},
},
})
Type: Array
Default value: []
An array of grunt task to be 're-run'. Those should be long-living grunt task (like testacular server, express with keepalive and so on)
Type: Boolean
Default value: false
Wheter or not the rerun task should block or not. The preferred way is to leave keepalive to false and to useit in conjunction
with other long-living task like watch
Type: Number
Default value: 1247
The default port used for internal communication. The rerun:target task will launch a server listening on this port, wich will
recive further comunication via the rerun:target:task:go task.
In this example, the default options are used to so keepalive will be false and the port used internally will be 1247. So if the testing file has the content Testing and the 123 file had the content 1 2 3, the generated result would be Testing, 1 2 3.
grunt.initConfig({
watch: {
dev: {
files: ['server/*.js'],
//Note the :go flag used for sending the reload message to the rerun server
tasks: ['clean','rerun:dev:express:go']
},
},
express: {
dev: {
options: {
port: 3000,
bases: ['/public'],
keepalive: true,
server: path.resolve('./server/app.js')
}
}
},
// Configuration to be run (and then tested).
rerun: {
dev: {
options: {
tasks: ['express']
},
},
}
})
The project is in very ealry stage, so any suggestion, pull request and issue are welcomed. Please use github for any communication
(Nothing yet)
FAQs
Launch, relaunch and stop grunt task.
We found that grunt-rerun 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.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.