Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fatal error: ENOENT, no such file or directory #80

Open
jml6m opened this issue Nov 6, 2015 · 1 comment
Open

Fatal error: ENOENT, no such file or directory #80

jml6m opened this issue Nov 6, 2015 · 1 comment

Comments

@jml6m
Copy link

jml6m commented Nov 6, 2015

I have a very simple clean task.

clean: {
    temp: {
        src: ['tmp', 'dist/app-tmp.js']
    }
}

I then run this watch task.

watch: {
   dev: {
    files: [ 'Gruntfile.js', 'app/*.js', 'app/**/*.js', 'app/**/*.html', '*.html', '**/*.scss' ],
    tasks: [ 'jshint', 'browserify:bundle', 'ngtemplates', 'concat:js', 'compass', 'copy', 'clean:temp' ],
        options: {
            atBegin: true
        }
    }
}

Here is a sporadic error I get:

Running "clean:temp" (clean) task
Cleaning tmp...OK

Done, without errors.
Fatal error: ENOENT, no such file or directory 'c:\Users\j***\tmp'

File "tmp" deleted.
// watch task will now restart from beginning

It's weird that the error is thrown but then the next message is that the directory was deleted. After this block gets printed, the watch task will simply start over again. NOTE: This error doesn't get thrown all the time, it's seemingly random.

Anyone else experiencing these problems? I'm developing on Windows 7 and that seems to be a common problem with grunt-contrib-clean but I was hoping I could add some code in my clean task to ensure this error doesn't get thrown.

@f-liva
Copy link

f-liva commented Apr 14, 2017

I'm with you, same behavior here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants