Why use mkdirp over fs (native)?
Just an FYI, you're creating directories with 0777 chmod permissions. Doesn't Joomla use 0755?

@C-Lodder mkdirp Is creating all the given folders recursively. About permissions I was thinking how that thing will possibly react in the windows system but since I don’t do dos anymore I decided to leave the mode as is. You can test this with mode: 0644 And let me know

Check my template repo. Comitted something yesterday to build the folders recursively using FS

@C-Lodder nice but it seems that fs-extra already has this functionality so neither own code or another package is needed for recursive folder creation

Shame Node don't use fs-extra natively. fs has some very annoying flaws in it :/

@brianteeman can you give this a quick run when you have a minute to ensure this still works on windows please

Will do after the ?

@SniperSister @rdeutz can you guys have a look at the ATT why drone isn't triggering for the last 2 builds of this PR please

@wilsonge npm i ran fine on windows. even seemed to be faster than before. Only thing to note is the following. No idea if its related to this PR or not so posting it

npm WARN acorn-dynamic-import@4.0.0 requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN ajv-keywords@3.2.0 requires a peer of ajv@^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN babel-loader@6.4.1 requires a peer of webpack@1 || 2 || ^2.1.0-beta || ^2.2.0-rc but none is installed. You must install peer dependencies yourself.
npm WARN sass-loader@5.0.1 requires a peer of webpack@^2.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN com_media@4.0.0 No repository field.

@brianteeman yes somehow we need to remove the node_modules in administrator/com_media. I can do it here or spin another PR

Just quick because ....

The volume cache plugin reacts to special directives in a commit message to provide additional functionality. Include one of the following directives somewhere in your commit message to trigger their respective actions:

[CLEAR CACHE]
instruct the plugin to clear the entire cache. This only influences the restoring step, the plugin will still rebuild cache if instructed to do so.
[NO CACHE]
instruct the plugin not to restore or rebuild cache for this build.

@dgrammatiko looks like a legit drone failure now

But ESLint exists in the package.json

It's mkdirp that's missing from the dependencies according to the error?

Thanks!