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

Empty dir cli not working #8

Closed
ProtocolNebula opened this issue Jan 22, 2021 · 0 comments
Closed

Empty dir cli not working #8

ProtocolNebula opened this issue Jan 22, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@ProtocolNebula
Copy link

🐞 Bug report

Description

When emptyDir launched, it fails with an error.

🔬 Minimal Reproduction

Execute:

npx fse-emptyDir anyFolderExistingOrNot

fse-emptydir it's not declared but is available in package.json

💻Your Environment

Node Version:

v12.16.1

fse-cli Version:

"@atao60/fse-cli": "0.0.39",

🔥 Exception or Error

npx fse-emptyDir ./build 
Be gone rapscalian...
(node:49264) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string or an instance of Buffer or URL. Received undefined
    at Object.readdir (fs.js:846:10)
    at go$readdir (/Volumes/Data/swagger-to-angular2/node_modules/@atao60/fse-cli/node_modules/graceful-fs/graceful-fs.js:202:23)
    at Object.readdir (/Volumes/Data/swagger-to-angular2/node_modules/@atao60/fse-cli/node_modules/graceful-fs/graceful-fs.js:184:12)
    at emptyDir (/Volumes/Data/swagger-to-angular2/node_modules/@atao60/fse-cli/node_modules/fs-extra/lib/empty/index.js:11:6)
    at emptyDir (/Volumes/Data/swagger-to-angular2/node_modules/@atao60/fse-cli/node_modules/universalify/index.js:5:57)
    at Object.job (/Volumes/Data/swagger-to-angular2/node_modules/@atao60/fse-cli/src/tasks/emptyDir.ts:33:5)
    at doit (/Volumes/Data/swagger-to-angular2/node_modules/@atao60/fse-cli/src/wrapper.ts:11:12)
    at cli (/Volumes/Data/swagger-to-angular2/node_modules/@atao60/fse-cli/src/cli.ts:6:5)
(node:49264) 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: 1)
(node:49264) [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.
@ProtocolNebula ProtocolNebula added the bug Something isn't working label Jan 22, 2021
@atao60 atao60 closed this as completed in 82c3ee2 Jan 24, 2021
atao60 added a commit that referenced this issue Jan 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant