Closed toby1kenobi closed 5 years ago
@toby1kenobi Thanks for the tip on commenting out the clean task. I'm also on Windows 10 and am seeing the same issue. Unfortunately, it makes the grunt serve task basically unusable. Removing the clean task seems to be the workaround for now.
@toby1kenobi or @developering - if you're still using this project, and want to help us debug (a year later... eek).
I'm not a WIN user, but I believe it's a permissions issue. A couple things worth trying.
Try editing the clean task in grunt/clean.js
to this:
// Clean your /dist folder
module.exports = {
clean: ["dist/*"]
};
Check your permissions on the project root folder and dist/
, making sure they're writable.
@taeo it doesn't solve the problem.
@eldyvoon - I'm confused.
You say here "it doesn't solve the problem", then you submitted PR #89 which does exactly what I recommended in my suggestion 1 above in grunt/clean.js
changing ["dist"]
> ["dist/*"]
.
Please clarify + confirm my assumptions about your comments for me and anyone else reading this down the road.
dist/
writable does not solve the issue.@taeo, I made a PR but then later on I found that it doesn't solve the problem, simply ignore my PR. My workaround is to use grunt clean and grunt serve. Changing to ["dist/*"] doesn't help, try to add one new file while keeping grunt serve running.
Ok. I assume you are a WIN user? (I'm on a Mac and it's just fine)
To the best of my knowledge EPERM
is a windows specific, permissions related error.
Perhaps you could share your OS + Software versions for myself or others to help hone in on a fix?
Hey, if anyone is still having the issue: this code works for me.
module.exports = { clean: ["dist/*.html"] };
Hope it helps.
I have a weird problem I'm seeing on Windows 10. The first time I run grunt serve everything seems to be fine. Subsequently, however, it loads ok but as soon as I make a change in a template I get the following error:
It looks like server.js tries to access dist, which has just been removed by the clean task?
Once this has happened the only way I've found to get the serve task working again is by commenting out 'clean' in the default task (in grunt\aliases.yaml)