Currently, I'm experimenting with the grunt-concurrent task in order to utilize grunt-nodemon for watching my JS scripts. This setup allows me to concurrently use watch to continue executing concat and uglify on my files whenever they change.
Upon running grunt from the command line, an infinite loop is triggered, displaying:
Running "watch" task
Waiting...
Verifying property watch.concurrent.files exists in config...ERROR >> Unable to process task.
Warning: Required config property "watch.concurrent.files" missing.
To halt this continuous stream of messages, I am forced to exit the command line interface.
Here's a glimpse at my gruntfile:
(gruntfile content provided)
And here's a peek into my package.json file:
(package.json content provided)
UPDATE: RESOLVING THE INFINITE LOOP
While I haven't completely resolved the issue yet, progress has been made...
An oversight was discovered within my watch task:
watch: {
scripts: {
files: ['js/*.js'],
tasks: ['concat','uglify'],
options: {
spawn: false,
},
},
A crucial section was omitted:
watch: {
scripts: {
files: ['js/*.js'],
tasks: ['concat','uglify'],
options: {
spawn: false,
},
},
css: {
files: ['css/*.scss'],
tasks: ['sass'],
options: {
spawn: false,
},
}
},
This omission was causing malfunctions within the watch task. The continuous loop issue has now been eliminated. Instead, the terminal displays:
(updated terminal logs provided)
Although it seems that nodemon is functioning properly, there is no indication of the watch task in action. Furthermore, when modifying my SCSS file, there are no observable changes. Ideally, I would like grunt-concurrent to manage both nodemon and watch simultaneously.
Should successful execution produce different output in the command line?
Appreciate any assistance!