Error generating assets

[Techn1c4l]

Attempting to execute framework7 assets command results in the following error:

- Generating assets (Please wait, it can take a while)(node:11480) UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, mkdir 'D:'
    at Object.mkdirSync (fs.js:841:3)
    at ...AppData\Roaming\npm\node_modules\framework7-cli\utils\fs-extra.js:23:12
    at Array.forEach (<anonymous>)
    at Object.mkdirSync (...AppData\Roaming\npm\node_modules\framework7-cli\utils\fs-extra.js:19:25)
    at resizeImage (...AppData\Roaming\npm\node_modules\framework7-cli\assets\index.js:181:11)
    at ...AppData\Roaming\npm\node_modules\framework7-cli\assets\index.js:220:11
    at Array.forEach (<anonymous>)
    at handlePreset (...AppData\Roaming\npm\node_modules\framework7-cli\assets\index.js:206:32)
    at ...AppData\Roaming\npm\node_modules\framework7-cli\assets\index.js:236:9
    at Array.forEach (<anonymous>)
(node:11480) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:11480) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.