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

Issue with node 14 #7

Open
f-lehmann-gmx-de opened this issue Sep 11, 2020 · 1 comment
Open

Issue with node 14 #7

f-lehmann-gmx-de opened this issue Sep 11, 2020 · 1 comment

Comments

@f-lehmann-gmx-de
Copy link

f-lehmann-gmx-de commented Sep 11, 2020

When you exchange your project to node 14 and latest grunt version and you use grunt-mkdir, in that case you have to set the mode. Without the mode the system is not able to create the directories.
Looks like with node 14 the umask is not per default 0700.
eg. which is working in your code

            options: {
                mode: 0777,   <====== required now but the number can be different e.g. 0700...
                create: ['./tmp/a']
            }
@MarkusDeutschmann
Copy link
Contributor

MarkusDeutschmann commented Dec 8, 2020

I think it is because node 14 handles null differently: nodejs/node#32726

To fix the issue and restore the old behavior for NodeJS 14 the 4th line of src/mkdir.coffee must be changed from
mode: null
to
mode: undefined

That will then change the 5th line in the generated tasks/mkdir.js file from
mode: null,
to
mode: void 0,

That seems to be enought to make it work again in NodeJS 14 again.

To make it also able to run the grunt build & grunt test commands also the used grunt-mocha-cli package needs to be updated:
"grunt-mocha-cli": "^1.14.0"

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